[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn log lines (was Re: How does log translate to diff)

From: Adrian Robert <arobert_at_cogsci.ucsd.edu>
Date: 2004-02-10 16:10:26 CET

Probably it will be useful to wait for more feedback, but do you see
anything wrong with the points that:

1) having the "X lines" in the log output is confusing for ex-CVS users
due to the mis-parallel with CVS logs

2) it would be nice to have the "+/- lines" added to 'svn log -v'

If not, should I submit enhancement requests on the bugzilla? I can
understand that adding (2) might be hard if that info is not readily
available within subversion, but addressing (1) by putting the lines in
only under an option to svn log that parsers can use seems easy...


On Feb 9, 2004, at 4:10 PM, kfogel@collab.net wrote:

> Yes, the line count was added for guaranteed parseability, in case a
> log message by chance included the separator line.
> Holger Krekel <pyth@devel.trillke.net> writes:
>> hmmm, i wonder if parsers shouldn't just go for the much more
>> machine-readable xml-format, anyway.
> Some parsers do, some don't. (The ones I write usually don't use the
> XML format.)
>> Btw, a friend and me have written a higher level python abstraction
>> for svn-stuff and it's mostly a pain to parse 'svn' output apart from
>> 'svn log --xml'.
> Now that's just FUD :-). I've written such parsers multiple times in
> different languages, using the line count, and it was very easy.
> -Karl

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 10 16:18:10 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.