From: Steven Grimm <koreth@midwinter.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-add fails after file type change
Date: Sat, 16 Dec 2006 10:44:37 -0800 [thread overview]
Message-ID: <45843E95.2000101@midwinter.com> (raw)
In-Reply-To: <em1e1v$lse$1@sea.gmane.org>
Jakub Narebski wrote:
> Works if you use "git mv dir dir.real".
>
This came up during my testing of snapshot backups. The *real* sequence
is more like
$ git checkout -b new-snapshot
$ rsync /live/directory .
$ git add .
In other words, I don't know in advance that there's a rename or (short
of turning on verbose rsync output and parsing it) which parts of the
tree have changed at all. So I can't easily use git-mv here.
It still feels like a bug that "git add" can fail with no useful
diagnostic. It actually took me a fair while to figure out what was
going on here -- at first I thought it was having trouble with symlinks
in general, then with absolute-path symlinks (which the actual symlink
in question is), then I thought maybe it was a corrupt index. It wasn't
until I went back and looked at the previous snapshot that I was
overlaying this one on top of that I realized there used to be a
directory where that symlink lives now.
next prev parent reply other threads:[~2006-12-16 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 18:16 git-add fails after file type change Steven Grimm
2006-12-16 18:31 ` Jakub Narebski
2006-12-16 18:44 ` Steven Grimm [this message]
2006-12-16 18:35 ` A Large Angry SCM
2006-12-16 21:58 ` Junio C Hamano
2006-12-16 22:40 ` Steven Grimm
2006-12-17 0:19 ` Steven Grimm
2006-12-17 0:46 ` Junio C Hamano
2006-12-17 1:39 ` Junio C Hamano
2006-12-17 9:11 ` [PATCH] git-add: remove conflicting entry when adding Junio C Hamano
2006-12-16 19:23 ` git-add fails after file type change 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=45843E95.2000101@midwinter.com \
--to=koreth@midwinter.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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.