[Chandler-dev] Commit comments
bear at code-bear.com
Tue Jul 11 10:29:19 PDT 2006
Unless you modify the commit message *before* svn sends it to the
server no amount of hooking or processing will allow you to add text to
the commit message that svn stores.
The commit emails have their information added to the message after the
fact, and as Grant has noted, do nothing for people who monitor svn log
What would be needed is a script that can be used by all devs to parse
the commit message and add data before passing it to svn. Or we just
modify the email side of the picture by adding code to the post-commit
script that sends out the emails.
On Jul 11, 2006, at 1:17 PM, Reid Ellis wrote:
> An ideal solution would be to take the two actions (marking bug
> "resolved" and committing the change) and merge them, so that the
> comment is only typed in once (but is useful in both places).
> So can we do this with an svn hook of some kind and certain keywords
> (like "fixes bug NNN", which everyone seems to use)? Given the highly
> non-uniqe situation, I would hope there are tools already out there
> that accommodate this workflow.
> On Jul 11, 2006, at 11:57, Bryan Stearns wrote:
>> 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.
>> Andi Vajda wrote:
>>> 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.
>>> 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
>>>> 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
>>>> 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.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "chandler-dev" mailing list
Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
bear at code-bear.com
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20060711/8606319a/PGP.pgp
More information about the chandler-dev