Re: Revision 2 [was Re: [PATCH] Fix for Issue #1093 (pre-release)]
From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-10-29 20:51:17 CET
"C. Michael Pilato" <cmpilato@collab.net> writes:
> Nah, that would just complicate things further. My suggestions:
Why rule 3?
> The "peg" revision is the one that is auto-populated in various
Does rule 3 apply? i.e. M < BASE and N < BASE?
> svn diff -rM:N repos-url@HEAD
Lets drop rule 3 and try a little scenario:
Rev 1: Add /trunk/foo and /trunk/bar
Using URLs
See the rev 2 diff using
svn diff -r1:3 url://.../trunk/bar
See the rev 3 diff using
svn diff -r1:3 url://.../trunk/bar_at_1
See the rev 7 diff using
svn diff -r6:8 url://.../trunk/bar_at_5
See the rev 8 diff using
svn diff -r6:8 url://.../trunk/foo_at_6
Using working copy paths trunk/foo and trunk/bar at BASE rev 6
See the rev 2 diff using
svn diff -r1:3 trunk/bar
See the rev 7 diff using
svn diff -rBASE:HEAD trunk/bar
See the rev 8 diff using
svn diff -rBASE:HEAD trunk/foo
Looks good so far, but what about these
svn diff -r1:3 trunk/foo@1
Do they show the rev 2 diff, the rev 3 diff, or cause an error?
-- Philip Martin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Wed Oct 29 20:52:08 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.