Re: git commit messages

[Shaun McCance <shaunm gnome org>]

On Thu, 2009-04-23 at 16:23 -0400, Owen Taylor wrote:
> On Thu, 2009-04-23 at 21:59 +0200, Vincent Untz wrote:
> > Le jeudi 23 avril 2009, à 15:42 -0400, Behdad Esfahbod a écrit :
> > > On 04/23/2009 08:47 AM, Loïc Minier wrote:
> > >> On Wed, Apr 22, 2009, Vincent Untz wrote:
> > >>> Frédéric (fredp) is suggesting to also propose a standard scheme to
> > >>> reference bugs that are fixed by a commit (so we can script things if
> > >>> it's needed one day -- that's similar to what Debian does).
> > >>>
> > >>> Something like "Closes: #123456" or "Fixes: #123456".
> > >>>
> > >>> This should probably live in the longer explanation since the short
> > >>> explanation is limited in size...
> > >>>
> > >>> (Then we can also reference other bug trackers when needed: bnc#12345,
> > >>> rh#12345, lp#12345, etc.)
> > >>
> > >>   That would be excellent, thanks!  However please consider using:
> > >>      GNOME #1234
> > >>   one issue with the Debian closes: is that it doesn't indicate Debian,
> > >>   which is why Nokia, Ubuntu etc. all use different prefixes to refer to
> > >>   their bugs.  Using "GNOME #1234" would allow terminals to link to
> > >>   bugzilla.gnome.org directly for instance.
> > >
> > > I prefer the more verbose "GNOME Bug #1234" in that case.
> > 
> > But I'm lazy. You'll likely get me to write bgo#1234 or gnome#1234, but
> > writing "GNOME Bug #1234" or "Novell Bug #1234", "Red Hat Bug #1234"...
> > it just won't work for me (and I would guess other people).
> 
> I have a certain fondness for
> 
>  http://bugzilla.gnome.org/show_bug.cgi?id=1234
> 
> Not that I want to *type* that but I can be ultimately lazy and
> cut-and-paste it in without fear of mistyping the bug number.
> 
> - Owen
> 
> [ Yes, it's not very compact ]

But it's certainly the easiest to parse for any crazy
kids out there who like building project trackers.

--
Shaun