On 09.09.2011 14:38, Maciej Bliziński wrote:
2011/9/9 Ben Walton <[email protected]>:
Does this help? Would re-runnable makepatch be worth the effort?
How about splitting makepatch in two parts:
mgar stagepatch
mgar makepatch
The first would run git stage -p + git commit. You would run it a
number of times until all changes would be committed. You'd then run
mgar makepatch to generate the patch files, update the Makefile, and
then go "mgar clean package" to test whether the build recipe works.
How would "make stagepatch" know of all the "areas" or "logical blocks"
of code
that you have changes in order to generate a patch for each particular
block?
--
Juraj Lutter | /\ ASCII Ribbon Campaign
otis (at) wilbury (dot) sk | \/ - NO HTML/RTF in e-mail
http://www.wilbury.sk/ | /\ - NO Word docs in e-mail
JID: otis (at) jabber (dot) vx (dot) sk
!07/11 PDP a ni deppart m'I !pleH
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.
