Sam Vilain <sam@xxxxxxxxxx> wrote: > Sam Vilain wrote: > > Sam Vilain wrote: > >> Previously, if you passed a revision and a path to svn, it meant to look > >> back at that revision and select that path. New behaviour is to get the > >> path then go back to the revision. The old syntax is selected with new > >> syntax PATH@REV. This new syntax is not supported by the old tools, so we > >> have to try both in turn. > > > > Blast, this analysis is wrong. Hold off, I'll see what's really going > > on and re-submit. > > ok, figured it out :) > > I was close! I was just thrown off by 'svn ls PATH@REV' > > The patch is the same, just the description has changed. > > Subject: [PATCH] git-svn: handle changed svn cp command-line syntax > > Previously, if you passed a revision and a path to svn cp, it meant to look > back at that revision and select that path. New behaviour is to get the > path then go back to the revision (like other commands that accept @REV > or -rREV do). The more consistent syntax is not supported by the old > tools, so we have to try both in turn. The @REV and -rREV distinction/ambiguity has always confused me in svn, too. It always seems that it needed to be one way sometimes, the other way at other times, and even _both_ at other times... -- Eric Wong - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
