On Tue, 21 Mar 2006 10:17:15 -0500 Michael Jennings <firstname.lastname@example.org> wrote: > On Tuesday, 21 March 2006, at 07:39:56 (+0100), > Kim Woelders wrote: > > > Will the new tree be a clone of the sf one so it's possible just to > > change the CVS/Root files in sf checkouts? > > Yes. I can provide a perl quickie for updating your checkout to those > who prefer to do it that way. Poor low bandwidth me would really like to see some sort of local cvs fixup script. Don't care what language, as long as it's simple and works. > > Will e16 be included in the new tree? > > Absolutely. Everything in /cvsroot/enlightenment on SF will be > carried over, including e16, e17, misc, e_modules, and eterm. Don't know if it's possible, but I think it would be a good idea to move evidence as well, if Azundris is willing, and bring it in from the cold. I have had to submit patches in the past when I have changed an EFL API that evidence used, it would be a lot simpler if I could just apply the API fixes directly. On the other hand, maybe evidence could be declared dead, and we can ignore it next time someone makes an EFL API change that breaks it. This current limbo state that it is in is not doing anybody any good. On the gripping claw, someone that likes to fix things when API changes break them (like me for instance) could be given dev access to evidence for the express purpose of fixing it when it gets broken.
Description: PGP signature