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

* Your Email Address
* Spam protection	Enter the letters below: .__ .___.. .. ..__. [__) _/ \| \|\ /[__] \| \./__.\|/\\| \/ \| \|
Comment	>>>> * 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@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.
Attachment
Watch this ticket