From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/1] send-email: allow to compose only prepared cover letter
Date: Wed, 14 Oct 2015 12:42:19 +0300 [thread overview]
Message-ID: <1444815739.8361.621.camel@linux.intel.com> (raw)
In-Reply-To: <xmqqa8rma2xx.fsf@gitster.mtv.corp.google.com>
On Tue, 2015-10-13 at 14:11 -0700, Junio C Hamano wrote:
> Andy Shevchenko <andriy.shevchenko@linux.intel.com> 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.
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 <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2015-10-14 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:12 [PATCH 1/1] send-email: allow to compose only prepared cover letter Andy Shevchenko
2015-10-13 21:11 ` Junio C Hamano
2015-10-14 9:42 ` Andy Shevchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1444815739.8361.621.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.