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

Re: Display log from a tag -> head

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-15 16:07:28 CET

On Mar 15, 2005, at 8:50 AM, Ronny T. Lampert wrote:

>>> consider I made a tag of a version into /tags/project-drop3.
>>> Now I want to see all changes since THAT tag like
>>> #> svn log --from /tags/project-drop3:HEAD or
>> logs between two tags." In your case, you'd want to compare
>> -rX:HEAD, where X is the revision of trunk where the tag was copied
>> from.
>> http://svn.collab.net/repos/svn/trunk/doc/user/cvs-crossover-
>> guide.html
>
> Thanks for the fast answer, but that method is the one I knew and
> wanted to avoid, because it's not "simple" :-)
>
> So how about introducing a short-cut-command?
>
> It would retrieve the last revision from the tag/branch/... and then
> do a log -r <last_from_branch>:HEAD.
>
> Maybe for 1.2 ? I'd fill in the feature-request if it is reasonable to
> you.
>

It's really hard to define such a feature... how would you define the
UI?

The problem is that you're making a whole lot of assumptions here about
the relationship between two URLs -- that they share history in a
really specific way.

Honestly, what I'd really like to see is a new feature like

       svn diff URL1 URL2 --short

Where --short (--quiet? whatever it's called) causes the diff command
to print nothing but the single-letter status codes that one normally
sees from 'update' or 'merge'. Then at least you'd be able to see the
list of files that changed between two branches. Not quite the same
thing as seeing the logs, but a lot of people have asked for this.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 15 16:09:55 2005

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.