On Sat, Mar 05, 2011 at 10:54:20AM +0100, Bryan Tong Minh wrote:
On Fri, Mar 4, 2011 at 10:09 AM, Thomas Bleher
<ThomasBleher(a)gmx.de> wrote:
(Small wish: it would be very helpful if every
commit message referencing a
bug would also include the one-line summary of the bug; that makes it much
easier to quickly determine what the bug is about and if a bug is relevant
for a specific environment. Thanks to all developers that already add this
information!)
I fully agree with this. A commit summary should be more than "Fixed
bug x" or "Follow-up rX: fixed some stuff" At minimum you can include
the bug summary in the commit message, or some other descriptive line
of what your commit purpose was.
I agree with the problem, here's an alternate solution that
doesn't require people to modify their commenting behavior.
Post-process the commit summary. Decorate 'bug x' with 'bug x:
"<bug summary>"' which could also be a hyperlink to the bug
report.
--
Charles Polisher