Mike & List Mike Noyes wrote the following at 17:28 25.11.2002:
Looks like the uclibc is quite a homogeneous group, so they could agree on the model. Or maybe the lead there just decided to go that way. With the consent of the lead developers of each branch it should be possible to build a tree which does not necessarily have to be maintained by the lead developer. But without his consent to allod/include modifications to the tree such a venture is near to pointless.Everyone, The bering-uclibc team is making good use of our cvs repository. We now have two release/branch source trees under construction in cvs.Other LEAF release/branch lead developers please take note of these source trees. I'd like to see more of this.
Maybe we could invite the lead developers of the various branches to mirror their respective cvs tree(s) to a public place where it is possible for the other developers to make branches/modifications which eventually would be either rejected or make it to the base. Of course this might change the development cycle a little.
Just my 2c
THINK
Püntenstrasse 39
8143 Stallikon
mailto:[EMAIL PROTECTED]
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
