All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Baumann <waste.manager@gmx.de>
To: cho <tobutaz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] git-svn not following svn moves
Date: Thu, 18 Oct 2007 14:13:28 +0200	[thread overview]
Message-ID: <20071018121328.GA5358@xp.machine.xx> (raw)
In-Reply-To: <ff7fhg$2eu$1@ger.gmane.org>

On Thu, Oct 18, 2007 at 11:20:16AM +0000, cho wrote:
> Hello,
> 
> I have a git-svn checkout that apparently did not follow a move correctly.
> The files are not present in an svn checkout, but are in a git svn clone.
> 
> According to a trac browser, some of the files that appear in my git 
> checkout had in fact been moved to their separate branch before doing git-
> svn clone. I noticed this when trying to commit changes to those files, 
> getting the error message:
> > Le système de fichiers ne contient pas cet élément: Fichier non 
> trouvé : transaction '3926-1', chemin '.../composants.py' at /home/marc/
> bin/git-svn line 2960
> It's a standard subversion error, "Filesystem has no item"
> 
> I've made a clean checkout (with today's 1.5.3.4.206.g58ba4), and I still 
> have the moved files present.
> The clone command is just:
> git svn clone --stdlayout svn+ssh://host/srv/subversion/proj/appli/proj
> 
> Tell me if I can give more info (the repository isn't public).
> 

Any chance you could provide a testcase which is similar to what happened
in your private repo so that the problem could be reproduced here?

-Peter

  reply	other threads:[~2007-10-18 12:13 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 [this message]
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

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=20071018121328.GA5358@xp.machine.xx \
    --to=waste.manager@gmx.de \
    --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.