From: Frank Schwidom <schwidom@gmx.net>
To: git@vger.kernel.org
Subject: Bugreport
Date: Fri, 19 Jan 2024 14:25:51 +0100 [thread overview]
Message-ID: <20240119132551.GA31532@debian64> (raw)
This bug exists in possibly all git versions.
$ git init
$ touch a.txt
$ ln -s a.txt d
$ git add .
$ git commit -m + .
[master (root-commit) f6b4468] +
2 files changed, 1 insertion(+)
create mode 100644 a.txt
create mode 120000 d
$ ls -la
total 12
drwxr-xr-x 3 ox ox 4096 Jan 19 14:10 .
drwxr-xr-x 4 ox ox 4096 Jan 19 14:04 ..
drwxr-xr-x 8 ox ox 4096 Jan 19 14:10 .git
-rw-r--r-- 1 ox ox 0 Jan 19 14:10 a.txt
lrwxrwxrwx 1 ox ox 5 Jan 19 14:10 d -> a.txt
$ rm d
$ mkdir d
$ touch d/b.txt
$ git add .
$ git commit . -m +
error: 'd' does not have a commit checked out
fatal: updating files failed
# I expect that git just replaces the link by the directory. But it makes problems.
# Workaround:
$ rm -rf d
$ git add .
$ git commit -m + .
[master 522e6db] +
1 file changed, 1 deletion(-)
delete mode 120000 d
$ mkdir d
$ touch d/b.txt
$ git add .
$ git commit -m + .
[master 8a125ee] +
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 d/b.txt
[System Info]
git version:
git version 2.43.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 6.1.0-8-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.25-1 (2023-04-22) x86_64
compiler info: gnuc: 13.2
libc info: glibc: 2.37
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
Thanks in advance,
Frank Schwidom
next reply other threads:[~2024-01-19 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 13:25 Frank Schwidom [this message]
2024-01-19 23:14 ` Bugreport brian m. carlson
2024-01-20 0:46 ` partial commit of file-to-directory change, was Bugreport Jeff King
2024-01-20 0:55 ` Junio C Hamano
2024-01-20 1:22 ` Junio C Hamano
2024-01-25 18:54 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2023-10-24 20:40 bugreport galo joel
2023-11-20 8:36 ` bugreport Thomas Guyot
2020-12-02 10:08 bugreport Ole M
2020-12-02 16:25 ` bugreport Stefan Haller
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=20240119132551.GA31532@debian64 \
--to=schwidom@gmx.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;
as well as URLs for NNTP newsgroup(s).