From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Timothy Rice <timothy.rice@unimelb.edu.au>
Cc: Todd Zullinger <tmz@pobox.com>,
Thomas Fischer <thomasfischer@fastmail.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
git@vger.kernel.org
Subject: Re: git rm bug
Date: Thu, 07 Jun 2018 00:51:15 +0200 [thread overview]
Message-ID: <87a7s7zfz0.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <20180606201012.GA2454@sleipnir>
On Wed, Jun 06 2018, Timothy Rice wrote:
>> 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>"
nit: The .gitkeep convention seems to be much more common in the wild
than .keep, and it's probably time we documented that somewhere, even
though it's not a magic .git* file like .gitattributes et al.
next prev parent reply other threads:[~2018-06-06 22:51 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
2018-06-06 20:20 ` Robert P. J. Day
2018-06-06 22:51 ` Ævar Arnfjörð Bjarmason [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7s7zfz0.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=thomasfischer@fastmail.com \
--cc=timothy.rice@unimelb.edu.au \
--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.
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).