git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cho <tobutaz@gmail.com>
To: git@vger.kernel.org
Subject: Re: [BUG] git-svn not following svn moves
Date: Fri, 19 Oct 2007 08:30:51 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.10.19.08.30.47@gmail.com> (raw)
In-Reply-To: 4717D85C.9050805@vilain.net

Le Fri, 19 Oct 2007 11:04:12 +1300, Sam Vilain a écrit :

> cho wrote:
>> svn ci -m 'Add README.'
# forgot this
svn up

>> 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?

It's the same, with --follow-parent and with --no-follow-parent .

      parent reply	other threads:[~2007-10-19  8:32 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
2007-10-19  7:51       ` cho
2007-10-19  8:17       ` cho
2007-10-19  8:30       ` cho [this message]

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=pan.2007.10.19.08.30.47@gmail.com \
    --to=tobutaz@gmail.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).