This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Etiquette when pinging patches?
- From: "Daniel Berlin" <dberlin at dberlin dot org>
- To: gcc at gcc dot gnu dot org, rdsandiford at googlemail dot com
- Date: Sat, 20 Sep 2008 19:02:32 -0400
- Subject: Re: Etiquette when pinging patches?
- References: <87abe3td3m.fsf@firetop.home>
Honestly?
You should use whatever gets a response.
If you are at the point you have to ping a patch, it obviously has
fallen through the cracks, and you should do whatever is necessary to
make sure it gets attention.
To that end, I would just use new threads, as they make it clear it is
not part of an ongoing discussion, and something that needs attention.
I assume you are already also CC'ing the maintainers you want to
review it (I find this is the #1 best way to get a response).
On Sat, Sep 20, 2008 at 4:50 AM, Richard Sandiford
<rdsandiford@googlemail.com> wrote:
> I don't want to waste everyone's time with protocol, but I was wondering:
> what's the etiquette when pinging patches? Should the ping be a reply
> to the original message (i.e. should it be in the same thread), or should
> it be a new thread? I was once asked to use new threads instead of the
> old one, so that's what I've been doing, but there have been two cases
> recently in which people responded to the original message after the new
> thread developed.
>
> Richard
>