From: Sam Vilain <sam@vilain.net>
To: cho <tobutaz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git-svn not following svn moves
Date: Fri, 19 Oct 2007 11:04:12 +1300 [thread overview]
Message-ID: <4717D85C.9050805@vilain.net> (raw)
In-Reply-To: <ff7m2j$2eu$2@ger.gmane.org>
cho wrote:
> I've surprised myself but yes, there is a simple testcase.
>
> svnadmin create repo
> svn checkout file://$PWD/repo checkout
> cd checkout/
> svn mkdir trunk tags branches
> svn ci -m 'Standard svn layout.'
> cd trunk/
> svn mkdir doc
> touch doc/README
> svn add doc/README
> svn ci -m 'Add README.'
> cd ..
> svn mv trunk/ branches/oldtrunk
> svn ci -m 'Moved trunk.'
> svn mkdir trunk
> svn ci -m 'New trunk.'
> cd trunk/
> touch THIS_IS_THE_NEW_TRUNK
> svn add THIS_IS_THE_NEW_TRUNK
> svn ci -m 'Add marker.'
> cd ../..
> git svn clone file://$PWD/repo --stdlayout git-clone
> cd git-clone/
> tree
>
> So the testcase basically involves moving the trunk.
> git-svn gets very confused and keeps a mixture of the old and new trunk.
Were you using --follow-parent or not?
Sam.
next prev parent reply other threads:[~2007-10-18 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 11:20 [BUG] git-svn not following svn moves cho
2007-10-18 12:13 ` Peter Baumann
2007-10-18 13:11 ` cho
2007-10-18 22:04 ` Sam Vilain [this message]
2007-10-19 7:51 ` cho
2007-10-19 8:17 ` cho
2007-10-19 8:30 ` cho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4717D85C.9050805@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=tobutaz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.