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

bad output format design issue: svn log -v format is not parseable :-(

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-04-03 02:43:59 CEST

Ben Collins-Sussman wrote:

> C.A.T.Magic wrote:
>
>> when looking at
>> http://svn.collab.net/repos/svn/branches/
>> how could one find ALL branches that were ever started?
>
> Run 'svn log' on the branches directory.

thanks :)

svn log -v http://svn.collab.net/repos/svn/branches/ >svnbranchlog

(ruby)

lines = File.readlines("svnbranchlog")
lines.each { |line|
     line.gsub!('\\','/')
     if ( line =~ /^ D \/branches\/[^\/]*$/i )
         print "#{line}"
     end
}

=====

the log command (+network transfer) took about 10 seconds
and produces ~1MB of output.
filterering on 'deletes' outputs 86 deleted files.

so far so good...

but now i have a --serious-- problem:

how can I tell, by looking at the output
    A \branches\release-0.28.0 (from \trunk:6846)
if this means the filename
     "\branches\release-0.28.0 (from \trunk:6846)"
or the file
     "\branches\release-0.28.0"
???
this is evil!

svn log -v "X:\Work\release-0.28.0 (from trunk6846)"
------------------------------------------------------------------------
r8 | cat | 2004-04-03 02:40:39 +0200 (Sat, 03 Apr 2004) | 1 line
Changed paths:
    A \trunk\release-0.28.0 (from trunk6846)
------------------------------------------------------------------------

there are several similar issues on other outputs throughout svn.
shouldn't these filenames and usernames be URL-encoded or escaped
everywhere!???

please help + fix.
:(
=======
c.a.t.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 3 02:44:17 2004

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

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