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 22:25:55 -0400 [thread overview]
Message-ID: <20190510022554.GD1281@homura.localdomain> (raw)
In-Reply-To: <20190509185136.GC14000@google.com>
On 2019-05-09 11:51 AM, Emily Shaffer wrote:
> I'm still not sure I see the value of the extra header proposed here.
> I'd appreciate an explanation of how you think it would be used, Drew.
I'm not just thinking about your run of the mill mail reader, but also
mail readers which are aware of git and could use it to provide
git-specific features for browsing patchsets. Distinguishing it from the
mecahnism used for normal conversation allows us to have fewer
heuristics in such software.
next prev parent reply other threads:[~2019-05-10 2:25 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
2019-05-09 18:51 ` Emily Shaffer
2019-05-10 2:25 ` Drew DeVault [this message]
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=20190510022554.GD1281@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