From: Johan Herland <johan@herland.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Peter Collingbourne <peter@pcc.me.uk>
Subject: Re: [PATCH] Remove empty directories when checking out a commit with fewer submodules
Date: Mon, 11 Jan 2010 10:32:45 +0100 [thread overview]
Message-ID: <201001111032.45637.johan@herland.net> (raw)
In-Reply-To: <alpine.DEB.1.00.1001110954410.4985@pacific.mpi-cbg.de>
On Monday 11 January 2010, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 11 Jan 2010, Peter Collingbourne wrote:
> > Change the unlink_entry function to use rmdir to remove submodule
> > directories.
>
> NAK. We should not even try to _unlink_ submodule subdirectories; it
> would be _way_ too easy to lose data that way. Remember, submodules
> are a totally different beast from regular files. They can contain
> valuable, yet uncommitted data, that is not even meant to be
> committed.
>
> So you say if the submodule directories are empty, it is safe? Not
> so. They will never be empty: there is always .git/, and _that_ can
> contain valuable information that you do not want to throw away, too.
> Think of unpushed branches, for example. That would be _fatal_ if
> you rmdir() that for me.
>
> So please, no,
I believe what Peter is referring to is the _empty_ directories (and
that includes no .git/) that are placeholders for submodules that are
deliberately not cloned/checked out. This lets you do things like:
git clone url:to/some/project
cd project
git checkout some-other-branch-with-different-submodules
git submodule update --init
Of course, once you clone/checkout a submodule, there will be contents
in that directory (including the .git/), and Git should not try to
remove it.
Have fun! :)
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2010-01-11 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 2:59 [PATCH] Remove empty directories when checking out a commit with fewer submodules Peter Collingbourne
2010-01-11 8:57 ` Johannes Schindelin
2010-01-11 9:32 ` Johan Herland [this message]
2010-01-11 9:45 ` Johannes Schindelin
2010-01-11 9:53 ` Junio C Hamano
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=201001111032.45637.johan@herland.net \
--to=johan@herland.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peter@pcc.me.uk \
/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).