All cool. Thanks.
This should probably be mentioned in the section of the manual
describing working with branches etc.
By the way, is there an inverse of --stop-on-copy, like a
--start-on-copy, that would only show you the changes made on the
branch itself?
Perry
Ben Collins-Sussman <sussman@collab.net> writes:
> On Thu, 2004-04-15 at 15:12, Perry E. Metzger wrote:
>> Is there any better way to know what the base version number of a
>> branch is than including "create branch foo" in the commit message and
>> noting that the commit message is associated with a particular
>> revision in svn log? One of my users is noting that figuring out the
>> base version for a branch is a bit cumbersome when you need to get it
>> for diff&merge purposes...
>
> 'svn log -v branchURL' shows changed paths. You don't need to read
> human log messages at all: just look for the 'copy' in the list of
> changed paths.
>
> Actually, the easiest solution is to run
>
> $ svn log -v --stop-on-copy source-branch-URL
> [...]
>
> This command will display every change ever made to the branch, but
> --stop-on-copy option will cause the output to stop as soon as detects a
> copy operation in the branch's history. By definition, then, the very
> last log entry printed will show the copy being made. It will look
> something like:
>
> r9189 | joe | 2004-03-22 10:10:47 -0600 (Mon, 22 Mar 2004) | 1 line
> Changed paths:
> A /branches/mybranch (from /trunk:9188)
>
>
--
Perry E. Metzger perry@piermont.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 15 22:33:43 2004