Andy Shevchenko [off-list ref] writes:
My often use case is to do:
% git format-patch --cover-letter --subject-prefix="PATCH vN" rev1^..revXYZ
% $GIT_EDITOR 0000-*
% git send-email 00* # assumes series less than 100 patches
% rm -f 00*
I guess this patch would not hurt too much, but the above would
vastly be improved if you used "-vN" option, instead of the
hand-rolled subject prefix, and dropped the last "rm -f" (which in
turn would mean you would want to use -o option to specify where to
keep the older iterations of the topic). Then you can easily refer
to cover letters and patches from previous rounds while preparing
the latest to send out.
On Tue, 2015-10-13 at 14:11 -0700, Junio C Hamano wrote:
Andy Shevchenko [off-list ref] writes:
quoted
My often use case is to do:
% git format-patch --cover-letter --subject-prefix="PATCH
vN" rev1^..revXYZ
% $GIT_EDITOR 0000-*
% git send-email 00* # assumes series less than 100
patches
% rm -f 00*
I guess this patch would not hurt too much, but the above would
vastly be improved if you used "-vN" option, instead of the
hand-rolled subject prefix, and dropped the last "rm -f" (which in
turn would mean you would want to use -o option to specify where to
keep the older iterations of the topic). Then you can easily refer
to cover letters and patches from previous rounds while preparing
the latest to send out.
Thanks!
The patch I sent was a modification of previous variant I have. It
unfortunately misses undef $compose; line in the first conditional
branch.
Besides that I found that --annotate might be a workaround and it comes
a burden of editor how to avoid editing every patch but first.
--
Andy Shevchenko [off-list ref]
Intel Finland Oy