On Mon, 2011-06-20 at 00:23 +0200, Erich Titl wrote: > Hi KP > > on 19.06.2011 20:48, KP Kirchdoerfer wrote: > ... > > > > - the current leaf/leaf repository consists now only of the "buildtool", > > the > > environment (buildtool, sources and build helpers) for Bering-uClibc4. > > > > Andrews proposal is to (once again and hopefully finally) move all the > > current > > "buildtool" content to a more speaking name: bering-uclibc4 directory. > > That way we may add more directories for development under leaf/leaf, like > > bering-uclibc5, bering-uclibc-mips, bering-uclibc-experimental..., > > developement trees, which may be added if branching gets too complicated, > > or > > to give other LEAF variants a place to live. > > > > > > Is that we can all agree with? > > Erich? > > As long as bering-uclibc4 is not the parent of bering-uclibc5 as > mentioned above. I woudl use something more neutral as the top level and > use GIT as the branch manager.
Everyone, I'd prefer us to move bering-uclibc to its own repository, and retain leaf for common packages (cvs examples: sourceforge, doc, etc.). Does this sound like a reasonable/logical split that will avoid confusion/future-problems? http://leaf.git.sourceforge.net/ leaf leaf leaf packages leaf bering-uclbic ... http://leaf.cvs.sourceforge.net/ http://leaf.cvs.sourceforge.net/viewvc/leaf/doc/ http://leaf.cvs.sourceforge.net/viewvc/leaf/sourceforge/ -- Mike Noyes http://sourceforge.net/users/mhnoyes http://www.google.com/profiles/mhnoyes ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
