git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: josht@us.ibm.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] git-format-patch: Make the second and subsequent mails replies to the first
Date: Mon, 10 Jul 2006 14:44:22 -0700	[thread overview]
Message-ID: <7vwtal9lu1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1152556878.8890.45.camel@josh-work.beaverton.ibm.com> (Josh Triplett's message of "Mon, 10 Jul 2006 11:41:18 -0700")

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.

  reply	other threads:[~2006-07-10 21:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 15:44 [PATCH] git-format-patch: Make the second and subsequent mails replies to the first Josh Triplett
2006-07-10 16:01 ` Johannes Schindelin
2006-07-10 16:29   ` Erik Mouw
2006-07-10 16:43     ` Josh Triplett
2006-07-10 20:25       ` Jakub Narebski
2006-07-10 18:41     ` [PATCH 1/3] " Josh Triplett
2006-07-10 21:44       ` Junio C Hamano [this message]
2006-07-14 17:16         ` Josh Triplett
2006-07-14 18:23           ` Junio C Hamano
2006-07-14 19:20             ` Josh Triplett
2006-07-14 19:32               ` Junio C Hamano
2006-07-15  7:45                 ` Petr Baudis
2006-07-15  8:10                   ` Junio C Hamano

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=7vwtal9lu1.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=josht@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).