From: Paolo Bonzini <bonzini@gnu.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Roman V. Shaposhnik" <rvs@sun.com>, git <git@vger.kernel.org>
Subject: Re: Questions on patch lifecycle
Date: Tue, 22 Apr 2008 08:30:11 +0200 [thread overview]
Message-ID: <480D85F3.5060707@gnu.org> (raw)
In-Reply-To: <20080422044336.GA29771@spearce.org>
> Acceptance needs to be watched for by the author by fetching Junio's
> nightly updates, and seeing if your patch made it into next, or into
> pu, or not at all.
Also, if it is not, you can use the "What's cooking" messages to
understand if it fell through the cracks of Junio's mailboxes or if he
just had no time to look at it.
Paolo
next prev parent reply other threads:[~2008-04-22 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 4:11 Questions on patch lifecycle Roman V. Shaposhnik
2008-04-22 4:43 ` Shawn O. Pearce
2008-04-22 6:30 ` Paolo Bonzini [this message]
2008-04-22 7:47 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=480D85F3.5060707@gnu.org \
--to=bonzini@gnu.org \
--cc=git@vger.kernel.org \
--cc=rvs@sun.com \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).