From: Eric Sunshine <sunshine@sunshineco.com>
To: Pratyush Yadav <me@yadavpratyush.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/1] worktree: delete branches auto-created by 'worktree add'
Date: Wed, 18 Dec 2019 14:34:06 -0500 [thread overview]
Message-ID: <CAPig+cQjL3Q0JFFK86+5Ee_-g_gmuiAD8f_kx5Z5NxG2ZEP7+Q@mail.gmail.com> (raw)
In-Reply-To: <20191218193129.hnvaetebih4y2slt@yadavpratyush.com>
On Wed, Dec 18, 2019 at 2:31 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
> On 14/12/19 09:44PM, Pratyush Yadav wrote:
> > When no branch name is supplied to 'worktree add', it creates a new
> > branch based on the name of the directory the new worktree is located
> > in. But when the worktree is later removed, that created branch is left
> > over.
> >
> > Remove that branch when removing the worktree. To make sure no commits
> > are lost, the branch won't be deleted if it has moved.
>
> Ping?
I scanned the patch when you sent it and will have a number of
comments to make when I find time to review it formally.
next prev parent reply other threads:[~2019-12-18 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 16:14 [PATCH 0/1] worktree: delete branches auto-created by 'worktree add' Pratyush Yadav
2019-12-14 16:14 ` [PATCH 1/1] " Pratyush Yadav
2019-12-18 19:31 ` Pratyush Yadav
2019-12-18 19:34 ` Eric Sunshine [this message]
2019-12-27 11:05 ` Eric Sunshine
2020-01-04 21:47 ` Pratyush Yadav
2020-01-05 5:32 ` Eric Sunshine
2020-01-06 4:20 ` Eric Sunshine
2020-01-06 18:01 ` Pratyush Yadav
2020-01-09 9:46 ` Eric Sunshine
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cQjL3Q0JFFK86+5Ee_-g_gmuiAD8f_kx5Z5NxG2ZEP7+Q@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).