From: Joel Brobecker <brobecker@adacore.com>
To: Sean Chen <sean.chen1234@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: The abbreviation in []
Date: Wed, 06 Jan 2010 08:35:00 -0000 [thread overview]
Message-ID: <20100106083504.GH24777@adacore.com> (raw)
In-Reply-To: <5e81cb501001060016o7d59ab43x93c24aaa3f4551a9@mail.gmail.com>
> Just now, I noticed another style like [RFA/commit] (written by you).
> What does it mean?
> http://sourceware.org/ml/gdb-patches/2009-12/msg00459.html
This is used often by the maintainers when they are about to commit
a patch, but would appreciate some feedback on it. We use this protocol
as an intermediate approach between the situation where we are checking in
a patch because we're sufficient confident about the patch, and the
situation where we're asking for approval because we're touching an area
that we don't know enough to commit without review.
It can be a useful approach because we know that a lot of patches are
hard to review for most maintainers, so feedback cannot always be
obtained. So we leave the patch out for a while, hoping for comment,
eventually committing it even if the email generated no comment.
As I said, this is used by the maintainers, so I don't know if it's
really all that useful to explain in the CONTRIBUTING file... By the
time someone gets promoted to maintainer, they should have picked up
this sort of idiosyncratic usage in our mailing list!
--
Joel
next prev parent reply other threads:[~2010-01-06 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 1:06 Sean Chen
2010-01-05 5:00 ` Joel Brobecker
2010-01-05 15:46 ` Sean Chen
2010-01-05 17:42 ` Joel Brobecker
2010-01-06 6:33 ` Sean Chen
2010-01-06 6:51 ` Joel Brobecker
2010-01-06 7:56 ` Sean Chen
2010-01-06 8:03 ` Joel Brobecker
2010-01-06 8:16 ` Sean Chen
2010-01-06 8:35 ` Joel Brobecker [this message]
2010-01-06 9:01 ` Sean Chen
2010-01-06 9:26 ` Hui Zhu
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=20100106083504.GH24777@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sean.chen1234@gmail.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