Re: svn log output style

On Dec 1, 2006, at 21:52, Thomas Harold wrote:

> So... looking at the output of "svn log" (with -v):

[snip]

> To be honest, it's not the greatest at using whitespace to make it
> easy to scan visually. The horizontal bar is a clear marker, but
> there needs to always be a blank line before it to make it
> effective. And maybe the blank line before the comment starts
> needs to be removed.
>
> For instance, I find the following to be slightly easier to read,
> even though the comment is now mashed up against the bottom of the
> "Changed paths" section:

[snip]

> Am I just being picky? Does it break too many 3rd party scripts if
> that whitespace is moved around?

You may be interested in this script:

http://subversion.tigris.org/tools_contrib.html#log_police_py

It lets you enforce one and only one newline at the end of the log.
It will not help, however, with removing the space between the list
of changed paths and the commit message. I personally like this blank
line, but I realize that doesn't help you. Changing this would likely
break any script parsing the output of svn log, so my guess is the
Subversion team would be unlikely to make any such change until
Subversion 2.0 at the earliest (since 1.x releases are supposed to be
compatible with one another), and even then only with good
justification.

You could also parse the output of svn log (or svn log --xml) and re-
output it in the format that you prefer. You could even alias this to
"svn log" in your shell.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org