git clone with --separate-git-dir destroys existing directory content
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | git clone: check for non-empty directoryt/ | +2 | 3 replies | |
| 2/2 | git clone: don't clone into non-empty directorybuiltin/ | +10 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] git clone with --separate-git-dir destroys existing directory content
Hi,
I found an issue with git clone, when using --separate-git-dir and that directory already exists, it's content is destroyed.
I have created a patch set on origin/next, but (as I have learned this the hard way) please let me know if this needs to be backported...
Ben...
Ben Wijen (2):
git clone: check for non-empty directory
git clone: don't clone into non-empty directory
builtin/clone.c | 12 ++++++++++-- t/t5601-clone.sh | 3 ++- 2 files changed, 12 insertions(+), 3 deletions(-)
Signature · 1 line
2.27.0