From: Hui Zhu <teawater@gmail.com>
To: Sean Chen <sean.chen1234@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: The abbreviation in []
Date: Wed, 06 Jan 2010 09:26:00 -0000 [thread overview]
Message-ID: <daef60381001060126h4600ea48t7b0bdd4e785ffe00@mail.gmail.com> (raw)
In-Reply-To: <5e81cb501001060101rb7375f6l2be2ff71ef645b4e@mail.gmail.com>
I think maybe you can add a contributors FAQ to WIKI.
Thanks,
Hui
On Wed, Jan 6, 2010 at 17:01, Sean Chen <sean.chen1234@gmail.com> wrote:
>> 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!
>
> Thanks for your explanation.
>
> I understand your concern. This is also an intermediate situation
> between adding it to CONTRIBUTING file or not. :) If add, CONTRIBUTING
> file will grow. Otherwise, new contributors have to guess it. I think
> a FAQ thread in the mailing list is also OK. If so, new contributors
> will search title “FAQ” in the mailing list to get the information.
>
> From now on, we can search “rfa rfc commit patch ob” to get the
> current thread. :)
>
> --
> Best Regards,
> Sean Chen
>
prev parent reply other threads:[~2010-01-06 9:26 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
2010-01-06 9:01 ` Sean Chen
2010-01-06 9:26 ` Hui Zhu [this message]
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=daef60381001060126h4600ea48t7b0bdd4e785ffe00@mail.gmail.com \
--to=teawater@gmail.com \
--cc=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