From: Thomas Fischer <thomasfischer@fastmail.com>
To: git@vger.kernel.org
Subject: git rm bug
Date: Wed, 06 Jun 2018 14:32:37 -0500 [thread overview]
Message-ID: <1528313557.2662346.1398855328.3E0F8023@webmail.messagingengine.com> (raw)
OVERVIEW
"git rm" will remove more files than specified. This is either a bug or undocumented behavior (not in the man pages).
SETUP
1. In a git repository, create an empty directory OR a chain of empty directories
$ mkdir -p path/to/some/
2. Create a file in the deepest directory and add it to tracking
$ touch path/to/some/file
$ git add path/to/some/file
$ git commit -m 'add path/to/some/file'
THE BUG
Run 'git rm' on the tracked file.
EXPECTED BEHAVIOR
$ git rm path/to/some/file
rm 'path/to/some/file'
$ ls path
to/
$ ls path/to
some/
Note that path/, path/to/, and path/to/some/ still exist.
ACTUAL BEHAVIOR
$ git rm path/to/some/file
rm 'path/to/some/file'
$ ls path
ls: cannot access 'path': No such file or directory
The entire chain of empty directories is removed, despite the fact the git outputs only "rm 'path/to/some/file'".
This ONLY occurs when all the directories in the chain are empty after the tracked file has been removed.
This behavior is NOT documented in the man pages.
I propose that 'rmdir' statements are added to 'git rm' output, or that the man pages be updated to reflect this behavior.
Best,
Thomas Fischer
next reply other threads:[~2018-06-06 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 19:32 Thomas Fischer [this message]
2018-06-06 19:33 ` git rm bug Robert P. J. Day
2018-06-06 19:47 ` Thomas Fischer
2018-06-06 19:51 ` Robert P. J. Day
2018-06-06 20:01 ` Todd Zullinger
2018-06-06 20:10 ` Timothy Rice
2018-06-06 20:20 ` Robert P. J. Day
2018-06-06 22:51 ` Ævar Arnfjörð Bjarmason
2018-06-06 20:11 ` Jeff King
2018-06-06 22:50 ` Ævar Arnfjörð Bjarmason
2018-06-06 19:54 ` Duy Nguyen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1528313557.2662346.1398855328.3E0F8023@webmail.messagingengine.com \
--to=thomasfischer@fastmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).