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

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.

-- 
Yao (齐尧)


  parent reply	other threads:[~2013-02-26  9:32 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 [this message]
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
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=512C80DA.5070600@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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