Re: doing a diff between the trunk and a tag

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]

> 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.

--
[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*.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org