From: Junio C Hamano <junkio@cox.net>
To: Josh Triplett <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: Fri, 14 Jul 2006 11:23:38 -0700 [thread overview]
Message-ID: <7v4pxkoxjp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 1152897407.5177.8.camel@josh-work.beaverton.ibm.com
Josh Triplett <josht@us.ibm.com> writes:
>> 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?
Eh, that's not what I meant.
I do not mind the code you added to log-tree.c and revision.h,
and honestly I do not care which of threading or non-threading
mode is the default, although I think your explanation that it
parallels what send-email does makes a lot of sense.
But I do mind that the code added by the first patch to
cmd_format_patch runs by default, and worse yet, there is no
option turn it off. Setting message_id and ref_message_id in
rev_info struct should be something the end user should ask for
explicitly by invoking the command with an option, perhaps
--with-message-id, which you probably would also want to turn on
when any of --no-thread, --thread or --initial-reply-to options
are given.
-
next prev parent reply other threads:[~2006-07-14 18:23 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
2006-07-14 17:16 ` Josh Triplett
2006-07-14 18:23 ` Junio C Hamano [this message]
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=7v4pxkoxjp.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).