From: Jeff King <peff@peff.net>
To: "Erik Brady -X (brady - ROBERT HALF INTERNATIONAL INC at Cisco)"
<brady@cisco.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] credential: ignore SIGPIPE when writing to credential helpers
Date: Thu, 29 Mar 2018 18:29:49 -0400 [thread overview]
Message-ID: <20180329222949.GA13017@sigill.intra.peff.net> (raw)
In-Reply-To: <E29A3311-D880-4872-835B-EF082EB2F70C@cisco.com>
On Thu, Mar 29, 2018 at 10:20:40PM +0000, Erik Brady -X (brady - ROBERT HALF INTERNATIONAL INC at Cisco) wrote:
> I appreciate your time. Quick Q... is there a way to track the patch
> through to release? If not I can just scan release notes/etc so no
> worries.
When the maintainer picks up the patch, he usually says something like
"thanks, will queue". Then you can track its progress either by:
- fetching from https://github.com/gitster/git, which has all of the
topic branches. Yours will be "eb/something", depending what Junio
names it. And then you can periodically "git branch -a --contains
eb/something" to see it progress through the various integration
branches ('pu', 'next', 'master'). The branches are described in the
"note from the maintainer" that's sent to the list periodically.
E.g.:
https://public-inbox.org/git/xmqqy3nt40pq.fsf@gitster.mtv.corp.google.com/
- alternatively, you can read the "What's cooking in git.git" messages
sent out by the maintainer a few times a week. E.g.:
https://public-inbox.org/git/xmqqefkm6s06.fsf@gitster-ct.c.googlers.com/
There your eb/something topic will be mentioned, along with the
status (where it is in the graduation cycle, what's coming next, and
if it's stalled, why).
We're in a release freeze right for v2.17 right now, so I'd expect your
patch to probably go to the 'maint' track and end up in v2.17.1.
Of course somebody else may see something wrong I didn't and ask you to
correct it, which would be in a reply to this thread. :)
-Peff
next prev parent reply other threads:[~2018-03-29 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 22:20 [PATCH] credential: cred helper fast exit can cause SIGPIPE, crash Erik E Brady
2018-03-29 11:19 ` Jeff King
2018-03-29 17:25 ` Erik Brady -X (brady - ROBERT HALF INTERNATIONAL INC at Cisco)
2018-03-29 17:55 ` Jeff King
2018-03-29 18:00 ` [PATCH] credential: ignore SIGPIPE when writing to credential helpers Erik E Brady
2018-03-29 21:51 ` Jeff King
2018-03-29 22:20 ` Erik Brady -X (brady - ROBERT HALF INTERNATIONAL INC at Cisco)
2018-03-29 22:29 ` Jeff King [this message]
2018-03-29 22:35 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180329222949.GA13017@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=brady@cisco.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).