[Chandler-dev] Commit comments

[Bryan Stearns]

I'll add a +1 to Jeffrey's suggestion, and a -1 to Andi's: I don't want 
the full comment history, but I would like the bug title, just so I can 
tell whether I want to look at the code or skip the commit message 
entirely. Yes, the bug is one click away, but doing that for every 
commit email defeats the goal of trying to trivially ignore the ones I 
don't care about.

Ironically, for me it's commits like Andi's that need this the most: I 
don't know the code at all (so the filenames in the commit don't tell me 
much), but as a client of the repository, I find out about repository 
nuances from some commits there. A little extra info (more than just a 
bug number) would help a lot in figuring out which ones to study more 
deeply.

...Bryan


Andi Vajda wrote:
>
> On Mon, 10 Jul 2006, Jeffrey Harris wrote:
>
>> Now that I'm back from my (very refreshing) three week vacation, I'm
>> reading through hundreds of commit messages instead of the more normal
>> few at a time, and my experience has prompted me to make a request.
>>
>> It would be really nice if I didn't have to click on bug URLs over and
>> over again to figure out what general problem was solved by a commit.
>>
>> I'd like to ask people to include a sentence about what the bug being
>> solved is, in addition to including a bug number and a summary of the
>> solution, when committing.
>
> -1
>
> I'm really against duplicating data, especially one mouse click away.
>
> I'd much rather implement a commit script that scans the commit 
> comment and mails whomever doesn't want to follow the link the full 
> comment sequence of the bug report from bugzilla.
>
> This is actually quite easy to do. Let me know if that'd help and if 
> you'd subscribe to such a service.
>
> Andi..
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev