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

Re: Diff tag against trunk head

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 23 Nov 2010 11:09:56 -0500

On Tue, Nov 23, 2010 at 10:39, Kevin Connor Arpe <kevinarpe_at_gmail.com> wrote:
> Hello,
> I am using the latest (stable) version on both Linux and WinSlows.
> For one of my repositories, I created a daily tag of a diary.
> Example:
> /project/trunk/important_stuff
> /project/tags/2010-11-20/important_stuff
> /project/tags/2010-11-21/important_stuff
> /project/tags/2010-11-22/important_stuff
> etc.
> Each morning I svn copy "important_stuff" (HEAD revision) to the tags
> area and commit.
> In theory, this will be used to easily find what changed day-over-day.
> Of course all of this is possible poking through svn logs, but I want
> to make this easier.
> My question: What is the SVN command to diff a file in a tagged set vs
> trunk head?
> Fantasy command:
> svn diff -r"tag:2010-11-21" -rHEAD /project/trunk/important_stuff/details.txt
> or...
> svn diff -r"trunk:HEAD" /project/tags/2010-11-21/important_stuff/details.txt
> I tried many different svn diff commands.  No luck.  I also did some
> heavy Google/StackOverflow searching.  No luck.

I'm trying to understand how this tagging & diffing between 2 paths is
better/easier than just keeping your single file, and diffing
yesterday's date against HEAD. For example:

svn diff -r {2010-11-22}:HEAD /project/trunk/important_stuff

Use the --summarize switch to just list the paths that have been
modified, if that's all you're after.

If you're just using the file important_stuff to just keep a running
changelog, using svn log with the revision range (yesterday to HEAD)
applied to the trunk URL could also work, with a little extra
scripting & parsing; especially if you can create an XSL stylesheet to
apply to the output of svn log --xml
Received on 2010-11-23 17:11:17 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.