From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: git-add fails after file type change
Date: Sat, 16 Dec 2006 16:46:10 -0800 [thread overview]
Message-ID: <7vvekb73jh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <45848CF8.4000704@midwinter.com> (Steven Grimm's message of "Sat, 16 Dec 2006 16:19:04 -0800")
Steven Grimm <koreth@midwinter.com> writes:
> A Large Angry SCM wrote:
>> Did you try "git-update-index --replace dir"?
>
> Turns out that doesn't work. It gives me the same error I get without
> the --replace option:
>
> error: dir: cannot add to the index - missing --add option?
> fatal: Unable to process file dir
"update-index --replace --add" would be the way.
$ git ls-files -s
100644 fa457baf8abbf5dd3bb4cbfab0c5a4cf0523d7f8 0 1/2
100644 00750edc07d6415dcc07ae0351e9397b0222b7ba 0 3
$ ls -F
./ ../ 1/ 3 .git/
There is file 1/2 in directory 1.
$ mv 1 tmp ; mv 3 1 ; mv tmp 3
$ ls -F
./ ../ 1 3/ .git/
I just swapped them.
$ git update-index --replace --add 1
$ git ls-files -s
100644 00750edc07d6415dcc07ae0351e9397b0222b7ba 0 1
100644 00750edc07d6415dcc07ae0351e9397b0222b7ba 0 3
You are allowing update-index to 'add' things so you would need
to say --add regardless of --replace (--replace is only to allow
removal of conflicting entries while adding). In the hindsight,
we could have implied --add with --replace, but that is the way
it is, and update-index is not a Porcelain so there is not much
point fixing it now.
But I think you helped me to spot a bug ;-).
$ git update-index --replace --add 3/2
$ git ls-files -s
100644 00750edc07d6415dcc07ae0351e9397b0222b7ba 0 1
100644 00750edc07d6415dcc07ae0351e9397b0222b7ba 0 3
100644 fa457baf8abbf5dd3bb4cbfab0c5a4cf0523d7f8 0 3/2
The entry '3' should have been removed when we did --replace.
This index cannot be written out as a tree:
$ git write-tree
You have both 3 and 3/2
fatal: git-write-tree: error building trees
Currently we need to remove '3' by hand X-<.
$ git update-index --remove 3
$ git ls-files -s
100644 00750edc07d6415dcc07ae0351e9397b0222b7ba 0 1
100644 fa457baf8abbf5dd3bb4cbfab0c5a4cf0523d7f8 0 3/2
$ git write-tree
77be0dd800d74913a90662e35215ee648815fc17
next prev parent reply other threads:[~2006-12-17 0:46 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
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 [this message]
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=7vvekb73jh.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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