[PATCH 0/2] git clone with --separate-git-dir destroys existing directory content · Ben Wijen <hidden> · 2020-07-01
[PATCH 1/2] git clone: check for non-empty directory · Ben Wijen <hidden> · 2020-07-01
Re: [PATCH 1/2] git clone: check for non-empty directory · Eric Sunshine <hidden> · 2020-07-01
Re: [PATCH 1/2] git clone: check for non-empty directory · Eric Sunshine <hidden> · 2020-07-01
Re: [PATCH 1/2] git clone: check for non-empty directory · Eric Sunshine <hidden> · 2020-07-02
[PATCH 2/2] git clone: don't clone into non-empty directory · Ben Wijen <hidden> · 2020-07-01
Re: [PATCH 2/2] git clone: don't clone into non-empty directory · Eric Sunshine <hidden> · 2020-07-01
Re: [PATCH 2/2] git clone: don't clone into non-empty directory · Ben <hidden> · 2020-07-02
Re: [PATCH 0/2] git clone with --separate-git-dir destroys existing directory content · Eric Sunshine <hidden> · 2020-07-01
[PATCH v2 0/1] git clone: don't clone into non-empty directory · Ben Wijen <hidden> · 2020-07-02
[PATCH v2 1/1] git clone: don't clone into non-empty directory · Ben Wijen <hidden> · 2020-07-02

Re: [PATCH 1/2] git clone: check for non-empty directory

From: Eric Sunshine <hidden>
Date: 2020-07-01 17:41:04

On Wed, Jul 1, 2020 at 12:00 PM Eric Sunshine [off-list ref] wrote:

[...] For instance, we might do this:
    rm -rf dst &&
    echo foo=bar >realgitdir/config &&

I meant to use '>>' here, not '>'.