On Jul 19, 2007, at 11:43 AM, Johannes Schindelin wrote:
I do not like it at all. "." already has a very special meaning.
It is a
_directory_, no place holder.
And we're talking about using it to describe the directory.
More and more I get the impression that this thread is just not
worth it.
The problem was solved long ago, and all that is talked about here
is how
to complicate things.
By solved, you mean ignored? There is no reason for git not to track
empty directories other than "we don't like it".
Some projects I work on require certain directories to exist in order
to run properly, but tend to occasionally do things like delete all
files in this required directory. So far, it hasn't been an issue
because I'm working solo and using git just to bar against
stupidity. Git's policy of "don't touch things I don't know about"
works. But if I ever had to have someone clone it, they'd need to re-
create the directories. In this case, empty directories are part of
the content I care about. Yes, I could have a script do it, but
that's a work around, not a solution.
In another case, I'm using creating a git repository out of source
that is distributed as occasional tarballs with patches in between.
Git's lack of ability to track the empty directories means that I can
NOT re-create appropriate tarballs for the states distributed only as
patches. Yes, I could add placeholder files, but then the state is
not identical.
There are use cases for tracking directories. I'll agree that it
shouldn't be used for every source tree. But there are cases where
it is useful and there's no reason to simply forbid it.
~~ Brian
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
