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

From: wafflecode@openmail.cc <wafflecode@openmail.cc>
Date: Sep 5, 2017, 22:17 UTC
Message-ID: <20170905221732.Horde.QL8bINNPhkH82YmIiqhsUY9@vfemail.net>
In-Reply-To: <f8ed8f0b-a2e1-9e7a-bf79-2b7629b838f2@web.de>

Quoting Torsten Bögershausen <tboegi@web.de>:

Show 15 quoted lines

>> 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 every directory.
>
>> If so, is there a way to do this
>> automatically during the conversion using "git svn" or the like?
>
> Not what I am aware of.
> And even if, the .empty files need to be removed, once the directory is
> removed.
> And we don't have logic for that, as far as I know.
>

So upon re-reading the git-svn docs, there apparently _are_ "--preserve-empty-dirs" and "--placeholder-filename=<filename>" options.

I'm not sure how I missed these.  :-/

If I understand correctly, it sounds like exactly what I want. i.e. a placeholder file being added (and tracked) to each empty folder. Are there known issues or limitations to be aware of?

Thank you, David

-------------------------------------------------

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!