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:51:54 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1806061550530.9562@localhost.localdomain> (raw)
In-Reply-To: <1528314421.2665575.1398886712.579F37CE@webmail.messagingengine.com>
On Wed, 6 Jun 2018, Thomas Fischer wrote:
> I agree that the entire chain of empty directories should not be
> tracked, as git tracks content, not files.
>
> However, when I run 'rm path/to/some/file', I expect path/to/some/
> to still exist.
why?
> Similarly, when I run 'git rm path/to/some/file', I expect
> path/to/some/ to exist, *albeit untracked*.
again, why?
> I do NOT expect git to *track* empty directories. But I also do NOT
> expect it to remove untracked directories.
why not?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2018-06-06 19:54 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
2018-06-06 19:47 ` Thomas Fischer
2018-06-06 19:51 ` Robert P. J. Day [this message]
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.1806061550530.9562@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).