[kforge-dev] grievous svn commit comment behaviour

John Bywater john.bywater at appropriatesoftwarefoundation.org
Fri Jun 3 08:07:13 UTC 2005

Hi Jo,

Great to meet you t'other day....

Jo Walsh wrote:

>i've been musing over this voracious svn commentary issue. i found
>that 'svn commit' would comment the directory i ran that it, with the
>comment i intended for the file below it; but that 'svn commit .'
>works downwards through the tree even more voraciously, and 'svn
>commit *' isn't an option.
>it is a little frustrating. i tend to make lots of small
>interconnected changes and commit lots at once, so everything gets
>similar commentary. in trying to make more granular ones i wonder at
>the fast-ticking version number, i suppose it will get up into the
>high hundreds without much effort, one just gets used to that?

Perhaps another option is individually to list files that are to be 

$ svn commit file1 file2 file3

Then (I would hope) there will be an atomic commit and limited comment 

>the line length chops off my comments which tend to be pretty verbose;

Perhaps write short lines?

>i have dodgy scripts to generate rss feeds of my cvs commit comments;
>i should like to replicate that.

Sounds nice ;-)

Bye for now,



More information about the kforge-dev mailing list