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

RE: Display log from a tag -> head

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-03-15 20:19:13 CET

Unfortunately, there's no good way to discover "where a tag (or branch) was
copied from". The trick "svn log --stop-on-copy" will tell you the revision
it was *checked in at*, but that doesn't tell what revision it was a copy
of, unless it was created by a URL-to-URL "svn copy" (in which case, it was
copied from the previous revision).

If you are using svncopy, it makes a nicely structured log message that
contains the original revision numbers:

------------------------------------------------------------------------
r123 | dworley | 2004-12-02 18:32:06 -0500 (Thu, 02 Dec 2004) | 4 lines

svncopy.pl: creating branch
        Copying from https://scm.example.org/rep/testproj/dworley/B2 122
                to https://scm.example.org/rep/testproj/dworley/B3

------------------------------------------------------------------------

Oddly enough, the --stop-on-copy option can be used to tell the last change
of the source directory before it was copied, by comparing "svn log
--stop-on-copy" with "svn log" -- the last revision in the second but not
the first contains the source directory with contents exactly the same as
the revision of the source directory that was copied.

Unfortunately, the repository contains this information, but there's no way
to get it to tell.

If you only want to know what files are changed, the "svn diff
--diff-cmd=/bin/true tag/xxx main" trick will suffice for file contents,
although added and deleted files might take more work.

Dale

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Tue Mar 15 20:22:30 2005

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

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