Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] gdb/CONTRIBUTE update
Date: Tue, 26 Feb 2013 09:38:00 -0000	[thread overview]
Message-ID: <20130226093829.GA5802@host2.jankratochvil.net> (raw)
In-Reply-To: <512C80DA.5070600@codesourcery.com>

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.

I do not speak here whether the patch itself should be included in the PING
mail again or not, I do not find that important and it is also not expressed
explicitly in the proposed paragraph above.


Thanks,
Jan


  reply	other threads:[~2013-02-26  9:38 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 [this message]
2013-02-26  9:52     ` Yao Qi
2013-02-26 13:16       ` Jan Kratochvil
2013-02-26 11:16     ` Pedro Alves
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=20130226093829.GA5802@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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