From: "Ping Yin" <pkufranky@gmail.com>
To: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>
Cc: "Jeff Whiteside" <jeff.m.whiteside@gmail.com>,
"Asheesh Laroia" <asheesh@asheesh.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: why still no empty directory support in git
Date: Tue, 30 Dec 2008 23:36:49 +0800 [thread overview]
Message-ID: <46dff0320812300736x78e0086dq14fbd2c2f8f7f8c2@mail.gmail.com> (raw)
In-Reply-To: <200812300758.41988.robin.rosenberg.lists@dewire.com>
On Tue, Dec 30, 2008 at 2:58 PM, Robin Rosenberg
<robin.rosenberg.lists@dewire.com> wrote:
> You can have an empty tree, but the index doesn't store them,
> so they would be lost on checkout/commit. Linus sketched a solution,
> but nobody took the bait. Seems doable if anyone really wants it, but
> I'm certain it adds a lot of special cases.
>
> Look for a discussion [RFC PATCH] Re: Empty directories... posted on 2007-07-19.
> It's in the middle of a long thread.
>
Thanks for pointing me to that thread. For other's convenience, the
begin of the thread is
http://article.gmane.org/gmane.comp.version-control.git/52813
next prev parent reply other threads:[~2008-12-30 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 3:42 why still no empty directory support in git Ping Yin
2008-12-30 5:10 ` Asheesh Laroia
2008-12-30 5:28 ` Jeff Whiteside
2008-12-30 6:58 ` Robin Rosenberg
2008-12-30 7:45 ` Junio C Hamano
2008-12-30 15:36 ` Ping Yin [this message]
2008-12-30 6:25 ` Asheesh Laroia
2008-12-30 8:43 ` demerphq
2008-12-30 8:58 ` Asheesh Laroia
2008-12-31 1:06 ` David Brown
2009-01-01 20:06 ` Jeff King
2009-01-02 18:55 ` Johannes Schindelin
2009-01-02 21:31 ` Asheesh Laroia
2009-01-08 7:12 ` Asheesh Laroia
2008-12-30 6:09 ` Liu Yubao
2009-01-01 2:50 ` Anatol Pomozov
2008-12-30 12:09 ` Johannes Schindelin
2008-12-30 14:21 ` Michael Gaber
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=46dff0320812300736x78e0086dq14fbd2c2f8f7f8c2@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=asheesh@asheesh.org \
--cc=git@vger.kernel.org \
--cc=jeff.m.whiteside@gmail.com \
--cc=robin.rosenberg.lists@dewire.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).