From: Drew DeVault <sir@cmpwn.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: git@vger.kernel.org
Subject: Re: Proposal: Remembering message IDs sent with git send-email
Date: Thu, 9 May 2019 12:50:25 -0400 [thread overview]
Message-ID: <20190509165025.GA18342@homura.localdomain> (raw)
In-Reply-To: <20190509001959.GB14000@google.com>
On 2019-05-08 5:19 PM, Emily Shaffer wrote:
> What I think might be useful (and what I was hoping you were going to
> talk about when I saw the subject line) would be if the Message-Id is
> conveniently stored during `git send-email` on v1 and somehow saved in a
> useful place in order to apply to the In-Reply-To field on v2
> automatically upon `git format-patch -v2`. I'll admit I didn't know
> about --in-reply-to=ask and that helps with the pain point I've
> experienced sending out v2 before.
--in-reply-to=ask doesn't exist, that's what I'm looking to add. This
convenient storage mechanism is exactly what I'm talking about. Sorry
for the confusion.
next prev parent reply other threads:[~2019-05-09 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 23:10 Proposal: Remembering message IDs sent with git send-email Drew DeVault
2019-05-09 0:19 ` Emily Shaffer
2019-05-09 16:50 ` Drew DeVault [this message]
2019-05-09 18:51 ` Emily Shaffer
2019-05-10 2:25 ` Drew DeVault
2019-05-09 20:14 ` Eric Wong
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=20190509165025.GA18342@homura.localdomain \
--to=sir@cmpwn.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
/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).