From: Jeff King <peff@peff.net>
To: Stephen & Linda Smith <ischis2@cox.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Eric Sunshine <sunshine@sunshineco.com>,
git@vger.kernel.org
Subject: Re: Picking up old threads/patches
Date: Thu, 7 Jan 2016 03:03:50 -0500 [thread overview]
Message-ID: <20160107080350.GA15453@sigill.intra.peff.net> (raw)
In-Reply-To: <3039057.pHpnyVLACL@thunderbird>
On Wed, Jan 06, 2016 at 08:59:52PM -0700, Stephen & Linda Smith wrote:
> > If Will isn't interested in finishing these two patches I will pick them
> > up [ ($gmane/271213), ($gmane/272180) ]
> >
> > After that I will check look at some of the others for which you've
> > asked for help.
>
> I started work on both of these rerolls this evening. Since I do not have the
> original emails I don't have the Message ID's which would allow me
> to add to the threads with the git send-email command. Do either of you have the
> message ID's?
If it's an ancient thread, it's not a big deal to just start a new
thread (especially if you reference the old one in the text so people
can dig it up if they really care).
But for reference, you can add `/raw` to the end of a gmane article URL
to get all the headers. E.g.:
$ gmane=http://article.gmane.org/gmane.comp.version-control.git
$ curl -s $gmane/271213/raw | grep -i ^message-id:
Message-ID: <CAAKF_ub5c+2vVmG161O6gnUUeEcNfDUMU=mtn+k0T8bC-9ZHPw@mail.gmail.com>
-Peff
next prev parent reply other threads:[~2016-01-07 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 2:44 What's cooking in git.git (Jan 2016, #01; Mon, 4) Stephen & Linda Smith
2016-01-05 3:36 ` Junio C Hamano
2016-01-05 4:32 ` Stephen & Linda Smith
2016-01-07 3:56 ` Picking up old threads/patches Stephen & Linda Smith
2016-01-07 3:59 ` Stephen & Linda Smith
2016-01-07 8:03 ` Jeff King [this message]
2016-01-07 13:29 ` Stephen & Linda Smith
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=20160107080350.GA15453@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ischis2@cox.net \
--cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.