"Derek Mahar" <DMahar@penson.ca> writes:
> Yes, I agree, this was the expected behaviour (i.e. Subversion is
> behaving correctly), but my point is that "svn log --stop-on-copy"
> does not under all conditions return the branch copy revision as the
> user might expect. If the user has done any other copy operation
> since that user created the branch, --stop-on-copy stops at that
> copy point rather than the branch copy point. Though it is the
> correct result, this is probably not the result that the user
> expected (or, in other words, the result that the user wanted).
Can you provide a recipe for this behavior? The --stop-on-copy option
should only apply when the target of the log operation was the thing
that got copied. In other words, if you do:
svn copy trunk branches/foo
...
svn copy trunk/junk branches/foo/junk
...
svn log --stop-on-copy branches/foo
Your log output should continue past the copy of the thing *into* your
branch, and stop with the copy that created your branch. If you've
found an instance where this is not happening correctly, please try to
come up with a reproducible recipe, because that is a bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 29 16:54:39 2004