Re: why still no empty directory support in git
- From
Anatol Pomozov <anatol.pomozov@gmail.com>
- Date
- Jan 1, 2009, 02:50 UTC
- Message-ID
- <3665a1a00812311850p59f0f5e7ode1853d26c30b26@mail.gmail.com>
- In-Reply-To
- <4959BB07.6000106@gmail.com>
Hi
On Mon, Dec 29, 2008 at 10:09 PM, Liu Yubao <yubao.liu@gmail.com> wrote:
Show 11 quoted lines
> > Ping Yin wrote: > > Yes, i know this topic has been discussed for many times. However, i > > am still not clear about the real reason. > > > > So which is the reason? > > > > 1. it's by design, intentional > It's saied somewhere git is a "stupid content tracker", it cares file content > not file name, and empty directories will complicate the merge algorithm > unnecessarily.
Could you please explain how will it complicate merging. What is the difference between merging 2 directories with 0 and 5 files and merging 2 directories with 5 and 10 files?
+1 that git should respect empty directories. Git should handle file content and not decide for user does he want to keep empty directory in the source tree or not.
-- anatol