From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [patch] gdb/CONTRIBUTE update
Date: Tue, 26 Feb 2013 11:16:00 -0000 [thread overview]
Message-ID: <512C9996.6000007@redhat.com> (raw)
In-Reply-To: <20130226093829.GA5802@host2.jankratochvil.net>
On 02/26/2013 09:38 AM, Jan Kratochvil wrote:
> On Tue, 26 Feb 2013 10:31:06 +0100, Yao Qi wrote:
>> On 02/22/2013 04:26 AM, Jan Kratochvil wrote:
>>> + Patch from a contributor needs a review with approval from
>>> + maintainer. Still you drive the review process and inclusion
>>> + process of the patch. If there is no reply in a week send a new
>>> + mail (not reply) with PING in its subject. Occasionally even
>>> + a PING^2 mail may be needed in another week of no replise.
>>> +
>>
>> Jan,
>> why do we have to post the patch again in the new mail instead of a
>> reply to remind maintainers to review? If the patch is still
>> applied clearly, I don't see the benefits of doing that.
>
> With a reply mail users (reviewers) which use sorting of mail folder by
> threads (in Mutt 'o' 't') get the PING mail put under the original mail which
> is far in the past and the PING mail gets hidden+forgotten again due to it.
>
> This even is not an idea of mine, it was concluded on some GNU Tools Cauldron.
Do you like it? I don't.
Interesting. I had seen some pings like that on the gcc list, but I never
understood why people preferred them that way.
One consequence of that model I've often seen in the gcc list (and even
there only a few people tend to ping that way) is occasionally we see
the reviewer OKing in reply to the ping email, instead of replying to
the original submission, which obviously happens because it was quicker
to the reviewer to just hit reply to the ping, read the patch in the
browser (following the url), and hit send. I don't like this because
it makes archaeology harder, and, people who are tracking the original
thread may not notice the patch had been approved or further discussion had
happened on another thread.
If someone is pinging me, I prefer a reply to the original thread. I'm
currently using Thunderbird, and it sorts threads by most recent reply,
not by original post date (which I find a more sensible default - why
would one want to sort by original post date by default?). A separate
email with an url means more work for me, as I then have to go look up the
thread in Thunderbird that corresponds to that url, instead of having it
already handy (as when the ping is in the same thread, and thus displayed
as a child of the original patch). That's just a silly indirection out of
email to then reply back through email. It's a little more work for the
pinger as well, who has to look up an url to put in the email.
--
Pedro Alves
next prev parent reply other threads:[~2013-02-26 11:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 20:26 Jan Kratochvil
2013-02-21 21:01 ` Tom Tromey
2013-02-26 9:32 ` Yao Qi
2013-02-26 9:38 ` Jan Kratochvil
2013-02-26 9:52 ` Yao Qi
2013-02-26 13:16 ` Jan Kratochvil
2013-02-26 11:16 ` Pedro Alves [this message]
2013-02-26 13:12 ` Jan Kratochvil
2013-02-28 20:01 ` Tom Tromey
[not found] ` <20130228212725.GA1848@host2.jankratochvil.net>
2013-03-01 16:27 ` Tom Tromey
2013-03-01 16:41 ` Jan Kratochvil
2013-03-01 16:51 ` Tom Tromey
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=512C9996.6000007@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=yao@codesourcery.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