Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: Petr Sorfa <petrs@caldera.com>,
	"gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH] DWARF support for .debug_loc offsets
Date: Thu, 11 Jul 2002 10:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0207111345420.5583-100000@dberlin.org> (raw)
In-Reply-To: <npu1n6w46q.fsf@zwingli.cygnus.com>

On 11 Jul 2002, Jim Blandy wrote:

> 
> A procedural nit: putting "PATCH" in the subject line means by
> convention that you've committed, or are about to commit, the patch in
> your message.  If you're submitting a patch for approval, you should
> put "RFA" in your subject.

You are aware, that the idea that putting [PATCH] in the line means you 
are committing a patch, is pretty much different than every other project?

Look at GCC, fer instance.
[PATCH] means it's a patch, to be looked at.  

It's very confusing to submit patches to GDB, when it's the only one with 
different procedures.

> 
> "RFC" and "WIP" I *think* both mean that you're just asking for
> comments, but you plan to revise the patch before really submitting it
> ("RFA").
> 
> 


  reply	other threads:[~2002-07-11 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11 10:37 Petr Sorfa
2002-07-11 10:49 ` Jim Blandy
2002-07-11 10:57   ` Daniel Berlin [this message]
2002-07-11 11:10     ` Jim Blandy
2002-07-11 13:58       ` Andrew Cagney
2002-07-11 11:03 ` Jim Blandy
2002-07-11 12:20   ` Petr Sorfa
2002-07-11 12:22     ` Jim Blandy
2002-07-11 12:44       ` Petr Sorfa

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=Pine.LNX.4.44.0207111345420.5583-100000@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=petrs@caldera.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