From: Eric Sunshine <firstname.lastname@example.org> To: Ben Wijen <email@example.com> Cc: Git List <firstname.lastname@example.org> Subject: Re: [PATCH 0/2] git clone with --separate-git-dir destroys existing directory content Date: Wed, 1 Jul 2020 11:39:46 -0400 Message-ID: <CAPig+cS6XnUK9MQL68_yoR9Gve4_itmawsd_0-yJr3S5=3-zPQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Wed, Jul 1, 2020 at 5:46 AM Ben Wijen <firstname.lastname@example.org> wrote: > I found an issue with git clone, when using --separate-git-dir and that directory already exists, > it's content is destroyed. Thanks for fixing this. > 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... Does this patch series depend on certain topics in 'next'? If not, please base it on 'master' instead. This will allow it to graduate from 'seen' to 'next' and eventually 'master' without being held back by any other topics in flight. On the other hand, if it does depend upon some topic in 'next', then it is a good idea to specify which specific topics it needs. That way, your patches will be able to graduate after those specific topics graduate rather than having to wait until _all_ of 'next' graduates (which could take forever).
next prev parent reply index Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 9:36 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 ` Eric Sunshine [this message] 2020-07-02 8:13 ` [PATCH v2 0/1] " Ben Wijen 2020-07-02 8:13 ` [PATCH v2 1/1] " 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='CAPig+cS6XnUK9MQL68_yoR9Gve4_itmawsd_0-yJr3S5=3-zPQ@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Git Mailing List Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/git/0 git/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 git git/ https://lore.kernel.org/git \ firstname.lastname@example.org public-inbox-index git Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git