Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Hi, > > On Thu, 19 Jul 2007, Tomash Brechko wrote: > >> A year or so ago I too would strongly advocate the need of tracking >> empty directories, permissions et al., it seemed so "natural" and "plain >> obvious" to me back then. But since that time I learned to appreciate >> the "contents tracking" approach, and now view directories (paths in >> general) only as the means for Git to know where to put the contents on >> checkout. This, BTW, is consistent with how Git figures container >> copies/renames. > > Thank you. It is my impression, too, that after a while it becomes > obvious what is good and what is not. > > FWIW I just whipped up a proof-of-concept patch (so at least _I_ cannot be > accused of chickening out of writing code): > > This adds the command line option "--add-empty-dirs" to "git add", which > does the only sane thing: putting a placeholder into that directory, and > adding that. Since ".gitignore" is already a reserved file name in git, > it is used as the name of this place holder. But that means that checkout will create a file .gitignore in previously empty directories, doesn't it? I think that the placeholder name should rather be ".". -- David Kastrup - 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
