From: "Steven J. Murdoch" <git+Steven.Murdoch@cl.cam.ac.uk>
To: git@vger.kernel.org
Cc: normalperson@yhbt.net
Subject: Preserving empty directories when doing a git-svn clone/rebase
Date: Sun, 15 Nov 2009 02:06:05 +0000 [thread overview]
Message-ID: <20091115020605.GE15966@cl.cam.ac.uk> (raw)
When git-svn clones a Subversion repository, any empty directories
appear to be silently dropped (tested using git version 1.6.5.2 on Mac
OS X Snow Leopard). This causes problems for using git with software
projects which depend on Subversion's ability to track empty
directories. I was recently caught out by this, and it was difficult
to debug what had gone wrong.
Would it be possible to change git-svn to handle this case? Since git
doesn't have the ability to track empty directories, probably the
simplest thing to do would be to automatically add a file (e.g.
.gitignore) to any empty directories. In theory this could cause
problems, but I would think the chances of this are far lower than
with the current behaviour.
I think this feature would help projects in which some contributors
are transitioning to git. It would especially be useful to novice
users of git, who are not aware of the potential problems with having
empty directories.
I see there was a discussion in 2006:
http://kerneltrap.org/mailarchive/git/2006/11/29/231586
However, since then I haven't seen any updates. The rationale behind
the original request still seems applicable today:
"I think there are many potential git users out there who are
currently svn users. And git-svn is a really nice way to get started,
but this sort of stumbling block could really turn people off. For
example, it made me look pretty dumb when I carelessly complained to
my colleague about his code not working and then it turns out to be
because my super-advanced scm tool "messed things up"."
(git-svn and empty directories in svn (was: [PATCH 1.2/2 (fixed)]
git-svn: fix output reporting from the delta fetcher))
Thanks,
Steven Murdoch.
--
http://www.cl.cam.ac.uk/users/sjm217/
next reply other threads:[~2009-11-15 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 2:06 Steven J. Murdoch [this message]
2009-11-15 5:02 ` PEBKAC or bug: unable to create path-like branch names Todd A. Jacobs
2009-11-15 5:36 ` Jacob Helwig
2009-11-15 7:36 ` Todd A. Jacobs
2009-11-15 7:55 ` Jacob Helwig
2009-11-15 7:16 ` Daniel Barkalow
2009-11-16 3:32 ` Preserving empty directories when doing a git-svn clone/rebase Eric Wong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091115020605.GE15966@cl.cam.ac.uk \
--to=git+steven.murdoch@cl.cam.ac.uk \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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.
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 NNTP newsgroup(s).