git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/1] send-email: allow to compose only prepared cover letter

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 13, 2015, 21:11 UTC
Message-ID
<xmqqa8rma2xx.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1444752768-82136-1-git-send-email-andriy.shevchenko@linux.intel.com>
Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
Show 5 quoted lines
> 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.

Previous: Andy ShevchenkoNext: Andy Shevchenko
Message 2 of 3 in “send-email: allow to compose only prepared cover letter”
  1. 1/1 send-email: allow to compose only prepared cover letterAndy Shevchenko, Oct 13, 2015
  2. Junio C HamanoOct 13, 2015
  3. Andy ShevchenkoOct 14, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.