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

Re: Revision 2 [was Re: [PATCH] Fix for Issue #1093 (pre-release)]

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-10-30 18:34:02 CET

Jack Repenning <jrepenning@collab.net> writes:

> At 10:07 PM -0600 10/29/03, C. Michael Pilato wrote:
> >Are you asking for the diff between the new README in trunk and the
> >old README in revision 15 of the branch?
> >
> > svn diff http://.../branches/BRANCHNAME/README@12 README
> >
> >Remember, the peg revision is the first thing used to narrow down a
> >hunt for history. *Then* the path. Then, given the resulting line of
> >history, you deal with any operative ranges.
> OK, good, thanks, now there's (I think) only one more question:
> suppose the two nodes you want to diff are distinct, and are neither
> of them visible anywhere in HEAD (because there's been a whole lot of
> this "rm/create instead of modify" going on). I need to specify
> revision info merely to find a tree where each node can be addressed
> (two different revision specs), and then still I need to specify the
> particular revisions to be compared. That's potentially two distinct
> nodes and four distinct revisions. Can the proposed syntax cover
> that?

I think in such a case, the burden is on you to perform the reduction
of those four revisions to two. That is, you're going to have to do
some legwork to find those nodes anyway, so do a little more and just
find the two node-revisions you want to diff. I'm really hesitant to
suggest such madness as 'svn diff url1@M@X url2@N@Y' or any similar
nonsense. And before you suggest 'svn diff -rX:Y url1@M url2@N', let
me position myself in the sill of CollabNet Chicago's 10th floor

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 30 18:35:22 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.