From: Steven Grimm <koreth@midwinter.com>
To: Bert Douglas <bertd@tplogic.com>
Cc: git@vger.kernel.org
Subject: Re: rename directory weirdness
Date: Thu, 26 Jul 2007 16:54:31 +0800 [thread overview]
Message-ID: <46A86147.4010403@midwinter.com> (raw)
In-Reply-To: <46A8519D.5050801@tplogic.com>
Bert Douglas wrote:
> $ mv dir1 dir2
> $ git add dir2
> $ git commit -a
>
> It popped up my editor with long list of files that it recognized as
> 'renamed'.
> But one file it listed as 'copied' and further down as 'deleted'.
>
> Why this one file out of thousands not recognized as 'renamed' ?
> Is this a sign of a problem ?
Are the contents of the file in question identical to those of some
other file in your directory tree? I've seen that happen too. There were
some proposed improvements to address this last time it came up on the
list, but I'm not sure if any of them actually made it into the code base.
-Steve
prev parent reply other threads:[~2007-07-26 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 7:47 rename directory weirdness Bert Douglas
2007-07-26 8:54 ` Steven Grimm [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=46A86147.4010403@midwinter.com \
--to=koreth@midwinter.com \
--cc=bertd@tplogic.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).