[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: commit type
From:       Johannes Schindelin <Johannes.Schindelin () gmx ! de>
Date:       2008-10-31 23:27:19
Message-ID: alpine.DEB.1.00.0811010025570.22125 () pacific ! mpi-cbg ! de ! mpi-cbg ! de
[Download RAW message or body]

Hi,

On Fri, 31 Oct 2008, 7rans wrote:

> David Symonds <dsymonds <at> gmail.com> writes:
> 
> > On Fri, Oct 31, 2008 at 10:58 AM, 7rans <transfire <at> gmail.com> 
> > wrote:
> > 
> > > Currently I achieve this by adding "[type]" to the end of my commit 
> > > messages. But of course that's less than optimal.
> > 
> > Why is that less than optimal? It seems a lot less intrusive than what 
> > you suggest.
> 
> Because it becomes formalized. Which means people can write tools other 
> people can use to work with them.

So you want to force this onto all Git users?

If yes: that murmur you hear in the background, it might well be the 
collective "thanks, but no thanks" of people who do not want that type of 
distinction between different commits.

If no: what would be the real difference from that suffix in the oneline?

Ciao,
Dscho
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]