From: Alexander Potashev <aspotashev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Alexander Potashev <aspotashev@gmail.com>
Subject: [PATCH 0/2] Allow cloning to an existing empty directory
Date: Fri, 9 Jan 2009 02:24:21 +0300 [thread overview]
Message-ID: <1231457063-29186-1-git-send-email-aspotashev@gmail.com> (raw)
The problem I experienced today was that I couldn't clone a repo to a
separate filesystem. I've created a new LVM volume, a FS on it (XFS)
and mounted it to a directory.
But wasn't able to clone the repo to that directory. It's impossible to
mount a FS to a non-existent directory, right? But Git refuses to clone
to an existing directory.
The solution in my first patch allows cloning to an existing empty
directory. However, there could be problems doing the same as I did
with XFS using ext2-like filesystems, because they have lost+found
directories, i.e. the root directory of those FSs is never empty.
The first patch adds a function (is_pseudo_dir_name) to compare a
string with "." and "..", the second patch reuses that function in
the rest of the code.
Alexander Potashev (2):
Allow cloning to an existing empty directory
Use is_pseudo_dir_name everywhere
builtin-clone.c | 8 +++++---
builtin-count-objects.c | 5 ++---
builtin-fsck.c | 14 ++++----------
builtin-prune.c | 14 ++++----------
builtin-rerere.c | 11 +++++------
dir.c | 31 +++++++++++++++++++++++--------
dir.h | 8 ++++++++
entry.c | 5 ++---
remote.c | 6 ++----
transport.c | 4 +---
10 files changed, 56 insertions(+), 50 deletions(-)
next reply other threads:[~2009-01-08 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 23:24 Alexander Potashev [this message]
2009-01-08 23:24 ` [PATCH 1/2] Allow cloning to an existing empty directory Alexander Potashev
2009-01-08 23:24 ` [PATCH 2/2] Use is_pseudo_dir_name everywhere Alexander Potashev
2009-01-09 7:03 ` Johannes Sixt
2009-01-09 7:22 ` Johannes Sixt
2009-01-09 8:33 ` Junio C Hamano
2009-01-09 10:24 ` Alexander Potashev
2009-01-10 2:48 ` Junio C Hamano
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=1231457063-29186-1-git-send-email-aspotashev@gmail.com \
--to=aspotashev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).