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

Re: [PATCH 1/3] git-format-patch: Make the second and subsequent mails replies to the first

From
Josh Triplett <josht@us.ibm.com>
Date
Jul 14, 2006, 17:16 UTC
Message-ID
<1152897407.5177.8.camel@josh-work.beaverton.ibm.com>
In-Reply-To
<7vwtal9lu1.fsf@assigned-by-dhcp.cox.net>
On Mon, 2006-07-10 at 14:44 -0700, Junio C Hamano wrote:
Show 14 quoted lines
> Josh Triplett <josht@us.ibm.com> writes:
> 
> > Add message_id and ref_message_id fields to struct rev_info, used in show_log
> > with CMIT_FMT_EMAIL to set Message-Id and In-Reply-To/References respectively.
> > Use these in git-format-patch to make the second and subsequent patch mails
> > replies to the first patch mail.
> >
> > Signed-off-by: Josh Triplett <josh@freedesktop.org>
> > ---
> > Resend of previous patch as part of new patch series.
> 
> While I understand what you said about imap-send, I really would
> feel better if this was optional.  Do not change the default
> output format, please.

So rather than the --no-thread option provided in the second patch of this series, you'd prefer a --thread option to enable setting the In-Reply-To/References headers?

Note that I based the direction of the --no-thread switch on git-send-email's inclusion of these headers by default with no way to turn them off, figuring that having an option to do so gave it an advantage over git-send-email while remaining consistent with it. I also figured that most people would not mess with the defaults, and thus the default should make a patch series more readable on mailing lists.

- Josh Triplett
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 13 in “git-format-patch: Make the second and subsequent mails replies to the first”
  1. git-format-patch: Make the second and subsequent mails replies to the firstJosh Triplett, Jul 10, 2006
  2. Johannes SchindelinJul 10, 2006
  3. Erik MouwJul 10, 2006
  4. Josh TriplettJul 10, 2006
  5. Jakub NarebskiJul 10, 2006
  6. 1/3 git-format-patch: Make the second and subsequent mails replies to the firstJosh Triplett, Jul 10, 2006
  7. Junio C HamanoJul 10, 2006
  8. Josh TriplettJul 14, 2006
  9. Junio C HamanoJul 14, 2006
  10. Josh TriplettJul 14, 2006
  11. Junio C HamanoJul 14, 2006
  12. Petr BaudisJul 15, 2006
  13. Junio C HamanoJul 15, 2006

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.