On Thu, 2012-08-09 at 08:42 -0400, Gary Oberbrunner wrote: […] > Hi Russel -- we haven't yet tried long-lived ongoing development on a > separate feature branch, but I see no reason that shouldn't work. For > simple patches, most people are submitting on the default branch, > which is simplest for maintainers to merge. I think you could work > either in a named branch, and submit pull requests from there (the > wiki has doc for how to merge those into the main repo), or in the > default branch of a separate scons-d repo and submit pull requests > from there. Either one involves a merge on the maintainer's end. I > don't think either one can cause a development freeze unless the patch > causes other outstanding patches to suddenly be un-mergeable (which I > hope will not happen). On your end if you want to work in a > combination of those two ways (work on a branch and periodically merge > to default and submit pull requests from there) that's fine too; I > don't think the maintainer's job will be any different if you work > that way.
My worry with the single repository with default a mirror and a named branch is that in order to process any pull requests you have to accept the presence of the named branch in the mainline repository? -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
