git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Cassar" <m.e.cassar@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [BUG] 'git mv a/fileA b/fileB' causes 'c/fileC' to be deleted
Date: Mon, 2 Oct 2006 11:33:09 +1000	[thread overview]
Message-ID: <750170aa0610011833n39271704q349d86af76832783@mail.gmail.com> (raw)
In-Reply-To: <7vpsdc0wkz.fsf@assigned-by-dhcp.cox.net>

On 10/2/06, Junio C Hamano <junkio@cox.net> wrote:
> There could be a bigger problem, but it does not seem to easily
> reproduce as you noted in the message.  It could be that some
> unrelated thing in the working tree is playing a role in this
> breakage, but I do not think of offhand what that is.

> [...]  Care to show a bit more details
> on your working tree?

Okay, I should stop being lazy and actually produce a minimal test-case.

Here we go:

--CUT--
#!/bin/bash

git init-db

mkdir papers
mkdir papers/unsorted
mkdir papers/all-papers
mkdir partA
echo 'moo' > papers/unsorted/Thesis.pdf
echo 'cow' > partA/outline.txt
echo 'this file has brackets in its filename' > 'papers/unsorted/(brackets).pdf'

git add  papers partA
git commit -m 'intial commit'

git mv papers/unsorted/Thesis.pdf papers/all-papers/moo-blah.pdf
git commit -m 'move a file'

cg log -f
--CUT--

The problem seems to have come from the fact that a file in the source
directory of the move contained brackets in its filename.Removing the
file causes the problem to go away.

Hope this helps a little,

Mike

  reply	other threads:[~2006-10-02  1:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-01 14:21 [BUG] 'git mv a/fileA b/fileB' causes 'c/fileC' to be deleted Michael Cassar
2006-10-01 17:34 ` Junio C Hamano
2006-10-02  1:33   ` Michael Cassar [this message]
2006-10-02  5:05     ` Junio C Hamano
2006-10-02  5:20       ` Junio C Hamano

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=750170aa0610011833n39271704q349d86af76832783@mail.gmail.com \
    --to=m.e.cassar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).