Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Ian Lance Taylor <ian@airs.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Use $(SHELL) when running mkinstalldirs
Date: Thu, 15 May 2003 19:59:00 -0000	[thread overview]
Message-ID: <ro1u1bwhthc.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <m3k7ctse0l.fsf@gossamer.airs.com>

On 14 May 2003 09:12:58 -0700, Ian Lance Taylor <ian@airs.com> said:

> I missed the Subject line conventions somehow.  Are they written
> down anywhere?

Hmm, we should put this in gdbint.texi or in MAINTAINERS or
somewhere.  Anyways:

RFA: request for approval.  Always include this if your patch needs
approval, and Cc: the appropriate maintainer(s).

RFC: request for comments.  This is typically used when you have some
big plan that you want comments on before you generate detailed
patches.  (Or when you have patches that work but aren't as elegant as
you'd like.)

PATCH: This is typically used for patches that don't require approval,
either because the submitter can approve them or because they're
simple enough to qualify as obvious.

If patches are for the testsuite or for the documentation, people
frequently indicate that as well: e.g. [rfa/testsuite].  Also,
sometimes people say [patch rfc] for patches that they can approve
themselves but that they wouldn't mind another set of eyes to look
over.  And if your patch is for a branch instead of mainline, then you
include the name of the branch instead of or in addition to "patch".

Andrew has started to use "commit" for patches that are being
committed immediately.  Personally, I usually post my (non-branch)
patches a day or two before committing them, and I leave the same
subject line when I post a message saying that I've actually commited
the patch, so I don't use "commit".

David Carlton
carlton@math.stanford.edu


      parent reply	other threads:[~2003-05-15 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  6:23 Ian Lance Taylor
2003-05-14 12:51 ` Andrew Cagney
2003-05-14 16:13   ` Ian Lance Taylor
2003-05-15 17:12     ` Andrew Cagney
2003-05-15 19:59     ` David Carlton [this message]

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=ro1u1bwhthc.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ian@airs.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