[Tickets #5284] Re: Move to subversion for Horde code repository

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=5284
-----------------------------------------------------------------------
 Ticket             | 5284
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | Move to subversion for Horde code repository
 Queue              | Horde.org Servers
 Type               | Enhancement
 State              | Assigned
 Priority           | 2. Medium
 Owners             | Horde Developers
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2007-11-02 03:56) wrote:

>>> * port post-commit checks (or replace with another commit diff
>>> mailing list - do we want to maintain the Chora links, or go with
>>> inline diffs, or ... ?)
>>
>> I'm not sure what you mean with that.
>
> Right now cvs at lists.horde.org gets the log message, list of changed 
> files, and links to chora. We could also do inline unified diffs, 
> colorized diffs, or some combination thereof.

I *hate* colorized inline diffs. I can see some use for unified diffs as
attachments, or even colorized diffs as attachments (I have seen a few that
really were unified diff, just colored) but I wonder if it's worth the
message bloat. I have no strong opinion about this, but I'm definitely
happy with the way it works now.

> Another idea I'd like to implement is to recognize #\d+ (# followed 
> by numbers) in log messages and have a post-commit script that posts 
> the log message and a link to the changeset to any bug mentioned in a 
> commit.

Yep.