From: Ben Wijen <ben@wijen.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>, Ben Wijen <ben@wijen.net>
Subject: [PATCH v2 0/1] git clone: don't clone into non-empty directory
Date: Thu, 2 Jul 2020 10:13:34 +0200 [thread overview]
Message-ID: <20200702081335.16786-1-ben@wijen.net> (raw)
In-Reply-To: <CAPig+cS6XnUK9MQL68_yoR9Gve4_itmawsd_0-yJr3S5=3-zPQ@mail.gmail.com>
Eric, thank you for your review.
With this update I have:
* rebased (and squashed) on master
* included your proposals for the test
* changed "destination path..." to "repository path..."
Ben...
Ben Wijen (1):
git clone: don't clone into non-empty directory
builtin/clone.c | 12 ++++++++++--
t/t5601-clone.sh | 4 +++-
2 files changed, 13 insertions(+), 3 deletions(-)
--
2.27.0
next prev parent reply other threads:[~2020-07-02 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 9:36 [PATCH 0/2] git clone with --separate-git-dir destroys existing directory content Ben Wijen
2020-07-01 9:36 ` [PATCH 1/2] git clone: check for non-empty directory Ben Wijen
2020-07-01 16:00 ` Eric Sunshine
2020-07-01 17:40 ` Eric Sunshine
2020-07-02 5:32 ` Eric Sunshine
2020-07-01 9:36 ` [PATCH 2/2] git clone: don't clone into " Ben Wijen
2020-07-01 16:10 ` Eric Sunshine
2020-07-02 7:50 ` Ben
2020-07-01 15:39 ` [PATCH 0/2] git clone with --separate-git-dir destroys existing directory content Eric Sunshine
2020-07-02 8:13 ` Ben Wijen [this message]
2020-07-02 8:13 ` [PATCH v2 1/1] git clone: don't clone into non-empty directory Ben Wijen
2020-07-06 22:40 ` Junio C Hamano
2020-07-10 8:47 ` [PATCH v3 0/1] " Ben Wijen
2020-07-10 8:47 ` [PATCH v3 1/1] " Ben Wijen
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=20200702081335.16786-1-ben@wijen.net \
--to=ben@wijen.net \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).