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

Re: Feature: PREV in URLs?

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-04-03 17:23:51 CEST

Tim Hill wrote:
> Hi, I don't want to clog-up the bug list if this has already been
> discussed...
> Has anyone thought about adding richer ways to specify revision
> numbers in a repository? Specifically, if I want to compare (say)
> "foo.c" at revision N, with "foo.c" as it existed before rev N, I
> can't currently do this without examining the log (or checking out
> rev N and using COMMITTED). This seems to me to be an area where svn
> is weak: I seem to be spending too much time scanning logs for
> information that svn should be able to supply automatically.
> Some examples of what I think would help:
> *- r N:-M * If "M" is negative, interpret as the absolute value
> "N-M" (e.g. "-r 10:-5" is the same as "-r 10:5"). The same can be used
> with N, so "-r -1:10" means "-r 9:10" or -r -1:HEAD means the head and
> previous revisions. Both N and M can't both be negative.

This is incredibly cryptic, and just a matter of simple arithmetic.

> *-r N:*M * The "*" means the "Mth" change to the item, going
> backwards in the log, and again either N or M can be qualified (but
> not both). So "-r *1:10" means revision 10 and the previous commit of
> the item (i.e. go back N log entries).

See "svn log --limit" (1.2 and later).

> Also, how about "*' by itself meaning the same rev # as the
> --stop-on-copy rev for the item (i.e. the last branch). So "-r *:HEAD"
> means the two revisions at each "end" of the branch?

Ideally, the syntax would allow you to specify "branch base" in such a way
that it still worked even if the branch was copied-and-modified in a single


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 3 17:26:54 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.