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

Re: doing a diff between the trunk and a tag

From: John Szakmeister <john_at_szakmeister.net>
Date: 2003-08-23 14:02:12 CEST

On Wednesday 20 August 2003 13:55, cmpilato@collab.net wrote:
> John Szakmeister <john@szakmeister.net> writes:
> > > Current, 'svn diff' doesn't support the comparitive working copy path
> > > case unless the paths being compared are the same and revision of one
> > > is BASE and the other is WORKING.
> >
> > The usage information seems to indicate that this should be supported,
> > although I do see in the code exactly what you are talking about.
> Yep. And maybe one day it well.


> > > That means something different. That means "show me my local mods in
> > > branch/tag1, and then show me my local mods in branch/tag2".
> >
> > Ah... That seems a little counter-intuitive. As a user I'd expect this
> > to work exactly the same as usage case 3.
> We've been around this bush before, and I think you're outnumbered
> here. For folks like me who often have multiple changes in progress
> in a given working copy, the ability to say 'svn diff
> subversion/libsvn_fs include/svn_fs.h subversion/tests/libsvn_fs >
> fs-changes.txt' is pretty valuable.[1]

I certain wasn't suggesting a change to it, just merely pointing out that it
seemed inconsistent.

> > svn diff --new=my_checkout_repo/README \
> > --old=file://<path to repo>/branches/tag1/README
> >
> > From the usage description, I would expect that this should work as well,
> > although in my setup, it is producing no output, and no error. If I
> > specify both with a URL I see the diff. But if one or the other is a
> > working copy path, I get nothing.
> That might actually be a bug. If you could send a small recipe using,
> say, the Subversion repository and a trunk checkout thereof, it would
> rock.

Hrmph. Well, I've updated to the HEAD version, and I don't see this problem.
Or perhaps I grew a brain, and I'm not doing something wrong anymore. :-)
Whatever the case is, I can't reproduce the problem (although, I swear I did
with svn 0.26).

> --
> [1] I made comments exactly opposite to this in previous threads on
> 'svn diff' syntax -- the behavior is so intuitive that I honestly
> didn't realize that I ran 'svn diff' in this fashion *all the time*.

I must admit that until I tried doing something a little unusual, I didn't
realize that I did the same as well. :-)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 23 14:02:50 2003

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.