From: wafflecode@openmail.cc
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: Empty directories in Git: Current guidance for historical commits?
Date: Tue, 05 Sep 2017 22:17:32 +0000 [thread overview]
Message-ID: <20170905221732.Horde.QL8bINNPhkH82YmIiqhsUY9@vfemail.net> (raw)
In-Reply-To: <f8ed8f0b-a2e1-9e7a-bf79-2b7629b838f2@web.de>
Quoting Torsten Bögershausen <tboegi@web.de>:
>> 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!
next prev parent reply other threads:[~2017-09-06 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 12:47 Empty directories in Git: Current guidance for historical commits? wafflecode
2017-09-05 17:58 ` Torsten Bögershausen
2017-09-05 22:17 ` wafflecode [this message]
2017-09-05 20:31 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170905221732.Horde.QL8bINNPhkH82YmIiqhsUY9@vfemail.net \
--to=wafflecode@openmail.cc \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).