On Sat, 2007-06-23 at 19:25 +0100, Peter TB Brett wrote: > Hi folks, > (3) From now on I'm going to maintain my patchset privately, and merge patches > only every now and again when either an urgent fix is needed or a release > is coming up. I will revert the .po changes from earlier, however.
This is similar to what I've been doing, however I don't think it fosters good reviewing practises. People read patches sent incrementally, and / or committed incrementally. Reading the change-sets of a big merge is more problematic. I don't know if a branch in the main repo is the best solution either (as we shouldn't ever re-write history etc, making publishing stg work harder). For these reasons, I advocate anyone working on changes "privately" should set up a mirror with repo.or.cz (or ask Ales for one on gpleda.org). This mirror could be more lax about history re-writing - so long as you tell people to expect it, you can fiddle about, and produce a nice clean series of patches / commits for eventual merging. In addition, how about Wiki page detailing who's working on what? (Possibly including details of work done, but not-yet merged, work in progress, and tasks people are committed to doing in the _short_ term future). Regards, Peter C. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
