Re: Empty directories in Git: Current guidance for historical commits?

2017-09-05 Thread wafflecode
Quoting Torsten Bögershausen : Is just dropping a ".gitignore" or "README" file in the empty directories during conversion still the most reasonable approach? A .gitignore will, but may cost 0.001% CPU time when running "git status". I have seen systems that create a file called ".empty" in

Re: Empty directories in Git: Current guidance for historical commits?

2017-09-05 Thread Jeff King
On Tue, Sep 05, 2017 at 12:47:43PM +, wafflec...@openmail.cc wrote: > Is just dropping a ".gitignore" or "README" file in the empty directories > during conversion still the most reasonable approach? Yes, I think so. > If so, is there a way > to do this automatically during the conversion us

Re: Empty directories in Git: Current guidance for historical commits?

2017-09-05 Thread Torsten Bögershausen
On 2017-09-05 14:47, wafflec...@openmail.cc wrote: > > Hello, > > Per the FAQ it's clear that Git (by current design) does not track empty > directories:  > https://git.wiki.kernel.org/index.php/GitFaq#Can_I_add_empty_directories.3F > > That's fine and I can fix that for my code going forward vi

Empty directories in Git: Current guidance for historical commits?

2017-09-05 Thread wafflecode
Hello, Per the FAQ it's clear that Git (by current design) does not track empty directories: https://git.wiki.kernel.org/index.php/GitFaq#Can_I_add_empty_directories.3F That's fine and I can fix that for my code going forward via the build system, as needed. However I'm looking to imp