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

Re: svn log --verbose not machine parsable?

From: Charles Lobo <charles.lobo_at_gmail.com>
Date: Thu, 12 Feb 2009 19:32:18 +0530

Update: I have found a way to parse it (below in chicken scheme).

(require 'regex)
(define (get-msg-line msg-line)
  (if (string-match ".*:.*" msg-line) ; when there is a path to check
      (set! msg-line ; strip (from /...$
            (cadr (string-match "(.*) \\(from /.*\\)" msg-line))))
  ;; Finally return the path only
  msg-line (substring msg-line 5))

If anyone sees any problems with it let me know.


On Thu, Feb 12, 2009 at 7:07 PM, Charles Lobo <charles.lobo_at_gmail.com> wrote:
> Hello,
> I was writing a script that needed, as one of it's steps, to find all paths affected by a given revision.
> I figured "svn log --verbose" would be a good way to do it but I'm running into problems.
> Specifically, when the revision is created by a "svn cp" the log message is no longer parse-able. Take for instance the following steps:
> $svnadmin create /new
> $svn co file:///new
> $cd new
> $touch "strange (from without closing filename"
> $svn add "strange (from without closing filename"
> $svn ci -m "Test Step 1: Created funny file name"
> $svn cp "strange (from without closing filename" "new strange (from filename"
> $svn ci -m "Test Step 2: Did a copy to check log --verbose output"
> Basically, I have created a file called "new strange (from filename" which is a copy of another strangely named file. Now when I run svn log --verbose on this file it gives an un-parseable output (only because this is a copy):
> $svn log --verbose -r 2
> ------------------------------------------------------------------------
> r2 | charles.lobo | 2009-02-12 19:08:28 +0530 (Thu, 12 Feb 2009) | 1 line
> Changed paths:
> A /new strange (from filename (from /strange (from without closing filename:1)
> Test Step 2: Did a copy to check log --verbose output
> ------------------------------------------------------------------------
> One of the reasons we selected svn was because it was supposedly easy to script. But this is throwing a spanner in the works.
> Can anyone help?
> cheers,
> /BD


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-12 23:24:24 CET

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.