From: Stephen & Linda Smith <ischis2@cox.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>, git@vger.kernel.org
Subject: Re: Picking up old threads/patches
Date: Wed, 06 Jan 2016 20:59:52 -0700 [thread overview]
Message-ID: <3039057.pHpnyVLACL@thunderbird> (raw)
In-Reply-To: <2143067.ZpDECoHz1r@thunderbird>
> 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?
next prev parent reply other threads:[~2016-01-07 3:59 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 [this message]
2016-01-07 8:03 ` Jeff King
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=3039057.pHpnyVLACL@thunderbird \
--to=ischis2@cox.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).