Re: [1.8.0] Tracking empty directories
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Feb 3, 2011, 10:07 UTC
- Message-ID
- <vpqbp2tqvm1.fsf@bauges.imag.fr>
- In-Reply-To
- <201102021921.53755.wjl@icecavern.net>
"Wesley J. Landaker" <wjl@icecavern.net> writes:
> 2) One of git's best strengths is that it's so easy to interact with other > SCM software, primarily because git's features are a SUPERSET of other SCMs. > However, almost every other SCM can track empty directories, except > git,
[...]
> 4) On many projects I work on with a huge number of people, the workflow > is to create a very, very intricate directory hierarchy skeleton, so that > it's clear to everyone where everything goes and how it is organized, even > before any work is started.
Just adding my 2 cents: my first clash with Git's non-management of empty directories was a combination of both. A colleague created an SVN project with several empty directories, along the lines of "Here it is. Now, put your stuff in there".
git-svn didn't import these empty directories (I think I actually could have worked around this with "git svn mkdirs"). Adding .gitignore files would have been a really dirty workaround since I didn't want to put Git stuff in the SVN repo.
I don't think my colleague did anything wrong, I did want to use Git, and that was still frustrating to see such a simple scenario not managed by my favorite tool.
So, yes, I can clearly leave without empty directory support, but that would be a nice addition to Git.
-- Matthieu Moy http://www-verimag.imag.fr/~moy/