git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Timothy Rice <timothy.rice@unimelb.edu.au>
To: Todd Zullinger <tmz@pobox.com>
Cc: Thomas Fischer <thomasfischer@fastmail.com>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>,
	git@vger.kernel.org
Subject: Re: git rm bug
Date: Thu, 7 Jun 2018 06:10:13 +1000	[thread overview]
Message-ID: <20180606201012.GA2454@sleipnir> (raw)
In-Reply-To: <20180606200137.GJ3094@zaya.teonanacatl.net>

> It does seem like something which could be noted in the git
> rm docs.  Perhaps you'd care to take a stab at a patch to
> add a note to Documentation/git-rm.txt Thomas?  Maybe a note
> at the end of the DISCUSSION section?

That same documentation could mention a common workaround for when someone
does really want to keep the empty directories:

$ touch ./path/to/empty/dir/.keep
$ git add ./path/to/empty/dir/.keep
$ git commit -m "Keep that empty directory because it is needed for <whatever>"

This would obviate the need for a new flag to switch behaviours.

~ Tim


  reply	other threads:[~2018-06-06 20:17 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
2018-06-06 20:01     ` Todd Zullinger
2018-06-06 20:10       ` Timothy Rice [this message]
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=20180606201012.GA2454@sleipnir \
    --to=timothy.rice@unimelb.edu.au \
    --cc=git@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    --cc=thomasfischer@fastmail.com \
    --cc=tmz@pobox.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).