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

From: Dirk Heinrichs <dirk.heinrichs_at_capgemini.com>
Date: Wed, 25 May 2011 07:43:37 +0200

Am Dienstag, 24. Mai 2011, 16:36:11 schrieb Varnau, Steve (Neoview):

> > 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?
>
> I find it is better for this use case to log from past forward to find this
> info. This is my trusty command to find a branch point:
>
> svn log -qv -r0:HEAD -l1 --stop-on-copy <URL to branch>

Sorry, but this also doesn't work for me (gives the wrong revision as per my
first mail).

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遝 68      | Web:  http://www.de.capgemini.com
D-40468 D黶seldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net

application/pgp-signature attachment: This is a digitally signed message part.

Received on 2011-05-25 07:44:23 CEST

This message: [ Message body ]
Next message: 宋哲: "can I use post-commit hook to produce a C header file?"
Previous message: Nico Kadel-Garcia: "Re: Is rep-sharing enabled by default?"
In reply to: Varnau, Steve (Neoview): "RE: Possible bug: --stop-on-copy stops too early"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]