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

Re: [rebase] `fatal: cannot force update the branch ... checkout out at ...` is confusing when it isn't active

From
Josh Soref <jsoref@gmail.com>
Date
Jul 12, 2023, 20:33 UTC
Message-ID
<CACZqfqDE-SCOqVX9a8KCLAn1zSVbYxuCeU8Y=3-nhj5wbL=AWQ@mail.gmail.com>
In-Reply-To
<xmqqbkghw4qd.fsf@gitster.g>
Josh Soref writes:
> fatal: cannot force update the branch 'main' checked out at
> '/private/var/folders/r3/n29fz25x72x191fdv6mhhr3m0000gp/T/tmp.fGD64HAf'
> It's true git in the repository does have a pin of sorts for the
> `main` branch and that `git-rebase` would be very upset if the
> branch's location were changed, but as an end user, the `main` branch
> is not checked out, the `next` branch is checked out.
Junio C Hamano wrote:
> Fair enough.  Perhaps "cannot force update the branch 'main' in use"
> would alleviate the confusion?
That would be better.

Even better would be to tell me what's using it (rebase). I'm not sure how possible that is.

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “[rebase] `fatal: cannot force update the branch ... checkout out at ...` is confusing when it isn't active”
  1. Josh SorefJul 12, 2023
  2. Junio C HamanoJul 12, 2023
  3. Josh SorefJul 12, 2023
  4. Junio C HamanoJul 12, 2023
  5. Re* [rebase] `fatal: cannot force update the branch ... checkout out at ...` is confusing when it isn't activeJunio C Hamano, Jul 12, 2023
  6. branch: update the message to refuse touching a branch in-useJunio C Hamano, Jul 21, 2023

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.