Re: Proposal: Remembering message IDs sent with git send-email

From: Emily Shaffer <emilyshaffer@google.com>
Date: May 9, 2019, 18:51 UTC
Message-ID: <20190509185136.GC14000@google.com>
In-Reply-To: <20190509165025.GA18342@homura.localdomain>

On Thu, May 09, 2019 at 12:50:25PM -0400, Drew DeVault wrote:

Show 12 quoted lines

> 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.

Looking at the documentation, I suppose I hadn't realized before that --thread will generate a Message-Id for your cover letter. It does seem like we could teach --thread to check for the previous patch's cover letter in the directory provided by -o. Of course, this wouldn't work if the author was generating v2 and didn't have the v1 files available (i.e. different workstation or different author picking up the set).

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 don't know much about emailed workflows outside of Git; is this something likely to be useful to other communities?

 - Emily