[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The fixes-bug field

From: Lars Ingebrigtsen
Subject: Re: The fixes-bug field
Date: Fri, 17 Jan 2014 16:57:43 +0100
User-agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux)

Stefan Monnier <address@hidden> writes:

>> With git, I'd prefer using a commit message that matches what's in
>> the ChangeLog entry, as that's simpler anyway.   I.e., I'd rather use
>> this commit message:
>>      Fix misdisplay of interlaced GIFs with libgif5 (Bug#16372).
> That's good enough for me, yes.  Having a more strongly formalized form
> (as used in Bzr) can be handy to add backlinks from the bug tracker's
> web pages to related commits, tho.

I'd suggest extending this to (fixes bug#16372).  That way you can refer
to bugs without saying that you've fixed them.  (I.e., the syntax is
(<command> bug#number [optional stuff]).)

And we can later implement a git commit hook that sends the correct
command to debbugs, so that all we have to do to fix and close a bug is
to check in and to push it.

That's what we do at work, and it works well for 97% of the use cases.

(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]