git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git branch doesn't allow me to forcibly delete branch which was checked out in a now-deleted worktree dir

From
Jacob Keller <jacob.keller@gmail.com>
Date
Jul 9, 2016, 04:58 UTC
Message-ID
<CA+P7+xoLKmUaJ9f1obVVDyjBTBe=XvSACvL8uiJWYf+2MTMN8w@mail.gmail.com>
In-Reply-To
<20160709022223.GC1916@gmail.com>
On Fri, Jul 8, 2016 at 7:22 PM, Erik Johnson <palehose@gmail.com> wrote:
Show 19 quoted lines
> On Fri, Jul 08, 2016 at 05:41:17PM -0700, Jacob Keller wrote:
>> It is possible we should update "git branch -d" should perform a
>> worktree prune first, since that would enable it to determine that you
>> deleted the directory, and any worktree which is removable should be
>> marked as persistent.
>>
>> Given that there is a known workaround (git worktree prune) and that
>> it is expected behavior for a branch checked out to prevent deletion,
>> I think the best coarse of action would be to patch git branch -d to
>> do a prune before attempting to delete.
>>
>> Thanks,
>> Jake
>
>
> Well, I never mentioned -d (I was using -D), but I think we're both in
> agreement.
>
>
Out of curiosity, what is git branch -D behavior when the worktree does exist?

Thanks, Jake

Previous: Erik JohnsonNext: Erik Johnson
Message 6 of 8 in “git branch doesn't allow me to forcibly delete branch which was checked out in a now-deleted worktree dir”
  1. Erik JohnsonJul 7, 2016
  2. Jacob KellerJul 7, 2016
  3. Erik JohnsonJul 8, 2016
  4. Jacob KellerJul 9, 2016
  5. Erik JohnsonJul 9, 2016
  6. Jacob KellerJul 9, 2016
  7. Erik JohnsonJul 9, 2016
  8. Duy NguyenJul 9, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.