This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Commit messages and the move to git

From: Segher Boessenkool <segher at kernel dot crashing dot org>
To: Joseph Myers <joseph at codesourcery dot com>
Cc: Jonathan Wakely <jwakely dot gcc at gmail dot com>, "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>, GCC Development <gcc at gcc dot gnu dot org>
Date: Mon, 4 Nov 2019 11:50:12 -0600
Subject: Re: Commit messages and the move to git
References: <f54f97d0-ed07-bfd6-ce1d-1f5e498f9697@arm.com> <CAH6eHdRpdjFwnwrM6EXN3nsz6nSvkyBpC4ZdxZqrt1f=TZsFuw@mail.gmail.com> <20191104173348.GB16031@gate.crashing.org> <alpine.DEB.2.21.1911041738430.12670@digraph.polyomino.org.uk>

On Mon, Nov 04, 2019 at 05:42:47PM +0000, Joseph Myers wrote:
> This is also why I don't care for [PATCH] tags at the 
> start of subject lines - they take away space for saying what the patch is 
> about, and on gcc-patches we can expect things are patches, [PATCH] 
> doesn't add useful information.)

Yeah, but various tools automatically add them (and v2 and 1/4 etc. tags,
which are extremely useful), so it would be very inconvenient to outlaw
them.  Oh, and it is what all of the rest of the world uses, I don't even
consciously *see* the standard stuff anymore, it's only when people get
creative ;-)

Segher

References:
- Commit messages and the move to git
  - From: Richard Earnshaw (lists)
- Re: Commit messages and the move to git
  - From: Jonathan Wakely
- Re: Commit messages and the move to git
  - From: Segher Boessenkool
- Re: Commit messages and the move to git
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]