From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13329 invoked by alias); 15 May 2003 19:59:01 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 13266 invoked from network); 15 May 2003 19:59:00 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by sources.redhat.com with SMTP; 15 May 2003 19:59:00 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h4FJwtn05547; Thu, 15 May 2003 12:58:55 -0700 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Ian Lance Taylor Cc: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: PATCH: Use $(SHELL) when running mkinstalldirs References: <20030514062315.8589.qmail@gossamer.airs.com> <3EC23BA9.2050409@redhat.com> From: David Carlton Date: Thu, 15 May 2003 19:59:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-05/txt/msg00252.txt.bz2 On 14 May 2003 09:12:58 -0700, Ian Lance Taylor 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