Peter Clifton wrote: > Being able to "float" patch series around and keep them up-to-date on > top of a changing remote repository is nice, but this is an extra > probably best tackled after basic git mastery.
Sure. Sounds like a motivator for change, though. >Peter TB Brett wrote: >This command works > by popping all the patches from the stack, pulling the changes in the > parent repository, setting the base of the stack to the latest parent > HEAD and pushing the patches back (unless '--nopush' is specified). > The 'push' operation can fail if there are conflicts. They need to be > resolved and the patch pushed again." > > HTH, Yep. That helped understand it is just right for keeping some code from bit rotting while reworking it to get consensus from the devel group. John Griessen (not wanting write acces to repos at the moment...) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
