--- Karl Fogel <kfogel@newton.ch.collab.net> wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
> > > the problem is that i was using HEAD and PREV,
> not explicit numbers,
> > > which do require a working copy.
>
> There should be some way to find out the
> last-changed-rev-before-N for
> any revision N on a given path, yeah. Or some
> option to diff such
> that
>
> $ svn diff --last-change -r100
> http://blah/foo/bar.txt
>
> does the equivalent of
>
> $ svn diff -r<N-1>:<N> http://blah/foo/bar.txt
>
> where N <= 100 is the revision where bar.txt last
> changed before 100.
>
> I'm not suggesting this is the ideal interface, just
> agreeing that we
> have a problem here, and that requiring people to
> have working copies
> to solve it is not a good answer :-).
I agree.
Would it be such a problem for the server to resolve
the special symbolic revision names (ie PREV, ...)?
Also, the more I think about it, the more I believe
that PREV should be a function so that things like
PREV(5), PREV(HEAD), PREV(PREV(HEAD)), and the like
can be done. In order to preserve backwards
compatibility, a default argument of, say, BASE (if
one exists) or HEAD (otherwise), can be used.
MTC,
Noel
__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 23:37:43 2002