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

Re: Possible bug: --stop-on-copy stops too early

From: Dirk Heinrichs <dirk.heinrichs_at_capgemini.com>
Date: Tue, 24 May 2011 12:31:01 +0200

Am Dienstag, 24. Mai 2011, 12:22:44 schrieb Stephen Butler:

> The "A", along with the "from <path>:<rev>", means that /software was
> copied from /PALISNC in this revision, so 'svn log --stop-on-copy' stops
> at this revision.
>
> I searched for "--stop-on-copy" in the bug tracker, and turned up
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=2518
> "Allow --stop-on-copy to traverse a fixed number of copies > 1"
>
> Unfortunately no one's picked it up yet. There's an interesting suggestion
> in the comments: the log shouldn't stop if the copy-source was deleted in
> the same revision. Of course, that assumes that the delete and the copy
> (the two halves of the renaming) were committed in the same revision.

Hmm, if it stops on _any_ copy, then maybe "svn log --stop-on-copy" is the
wrong command for finding the base rev of a branch. Is there a better
alternative?

Bye...

        Dirk

-- 
Dirk Heinrichs          | Tel:  +49 (0)211 56623 316
Configuration Manager   | Fax:  +49 (0)211 56623 450
Capgemini Deutschland   | Mail: dirk.heinrichs_at_capgemini.com
Wanheimerstraße 68      | Web:  http://www.de.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net

Received on 2011-05-24 12:31:55 CEST

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.