From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Roman V. Shaposhnik" <rvs@sun.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Questions on patch lifecycle
Date: Tue, 22 Apr 2008 00:43:36 -0400 [thread overview]
Message-ID: <20080422044336.GA29771@spearce.org> (raw)
In-Reply-To: <1208837481.26863.374.camel@goose.sun.com>
"Roman V. Shaposhnik" <rvs@sun.com> wrote:
> 0. Junio, are you the only Git maintainer or are there
> others responsible for particular subsystems of Git?
There are a number of subsystem maintainers, but most stuff
does go through Junio, yes.
> 1. What's the official way of submitting a patch?
> Is git-send-email(1) to this mailing list
> good enough? Does a submitter have to have
> a public tree that maintainer(s) can pull from?
Docmentation/SubmittingPatches
> 2. Once the patch is submitted how does the author
> get notified whether it is accepted, rejected
> or needs additional work.
Rejections get emailed to the author, and generally also to the list.
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.
If it isn't there after a couple of days and if you have also not
received a rejection notice indicating why it was not applied,
it probably got dropped. A polite reminder would then be OK.
--
Shawn.
next prev parent reply other threads:[~2008-04-22 4:44 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 [this message]
2008-04-22 6:30 ` Paolo Bonzini
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=20080422044336.GA29771@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=rvs@sun.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).