From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Thomas Fischer <thomasfischer@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: git rm bug
Date: Wed, 6 Jun 2018 15:33:27 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1806061532420.9259@localhost.localdomain> (raw)
In-Reply-To: <1528313557.2662346.1398855328.3E0F8023@webmail.messagingengine.com>
On Wed, 6 Jun 2018, Thomas Fischer wrote:
> 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'".
git cannot track empty directories. as that was the *only* content
in that whole hierarchy, the entire hierarchy had to be deleted.
rday
next prev parent reply other threads:[~2018-06-06 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 19:32 git rm bug Thomas Fischer
2018-06-06 19:33 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1806061532420.9259@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=thomasfischer@fastmail.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.
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).