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

Re: Strategy for computing "diff history" of an element?

From: David Weintraub <qazwart_at_gmail.com>
Date: Wed, 29 Jul 2009 21:40:55 -0400

You can use "svn log" on that one file to get all of the changed
revision numbers on that one file. You can use the SVN-API or just
parse the command line output.

If you're in a working copy:

     $ svn log someFile

If not:

     $ svn log svn://path/to/file

You can then use "svn diff -r$rev1:$rev2" to get the diff. The --diff-
cmd parameter is quite helpful since you can use your own diff command
instead of using the built in diff tool.

--
David Weintraub
David_at_Weintraub.name
Sent from my iPhone while riding in my Ferrari. (Jealous?)
On Jul 29, 2009, at 6:39 PM, "David M. Karr" <dk068x_at_att.com> wrote:
> With other SCMs, I've written scripts which would take an element name
> and run "<tool> diff" multiple times.  The first one would be the
> difference between HEAD and its predecessor.  The second one between  
> the
> pred of HEAD and its pred, and so on, until the element doesn't  
> exist at
> some earlier revision.  I'm trying to figure out how to write that  
> sort
> of script with Subversion.  To start, I don't see how to get a  
> revision
> number associated with HEAD, or get the predecessor of that revision
> number.
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376758
>
> To unsubscribe from this discussion, e-mail: [users- 
> unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376790
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-30 03:50:08 CEST

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.