From: wafflecode@openmail.cc
To: git@vger.kernel.org
Subject: Empty directories in Git: Current guidance for historical commits?
Date: Tue, 05 Sep 2017 12:47:43 +0000 [thread overview]
Message-ID: <20170905124743.Horde.bgYg8gUhE6ubSHtPAr3lCGl@vfemail.net> (raw)
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 import a fairly deep (10k+ commits) svn history
in to Git and I'm wondering what the current best practices are for
dealing with empty folders? Meaning to say, I'd like to be able to
check out an older revision of the code and have it build correctly
using the older build system which expects certain folders to exist.
There are a few different answers floating around the net, so I
figured I'd confirm via the mailing list.
Is just dropping a ".gitignore" or "README" file in the empty
directories during conversion still the most reasonable approach? If
so, is there a way to do this automatically during the conversion
using "git svn" or the like?
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 reply other threads:[~2017-09-05 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 12:47 wafflecode [this message]
2017-09-05 17:58 ` Empty directories in Git: Current guidance for historical commits? Torsten Bögershausen
2017-09-05 22:17 ` wafflecode
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=20170905124743.Horde.bgYg8gUhE6ubSHtPAr3lCGl@vfemail.net \
--to=wafflecode@openmail.cc \
--cc=git@vger.kernel.org \
/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).