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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux