Re: git switch error message tweak
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 17, 2020, 20:30 UTC
- Message-ID
- <xmqq8sgltoyb.fsf@gitster.c.googlers.com>
- In-Reply-To
- <BL0PR11MB34603334FD8AF4B662A74C3A9D9D0@BL0PR11MB3460.namprd11.prod.outlook.com>
Ed Avis <ed.avis@qmaw.com> writes:
Show 11 quoted lines
> To help those migrating from 'git checkout' to the newer 'git switch' > and 'git restore', this error message could be improved: > > % git switch baa022666d26a5d40e86c0b6349eb7435033e80a > fatal: a branch is expected, got commit 'baa022666d26a5d40e86c0b6349eb7435033e80a' > > It could print additionally > > To switch to this commit in 'detached HEAD' mode, use --detach. > > as long as it was indeed a commit that was given.
Excellent.
> I note also that while git checkout prints a spiel about "You are in > 'detached HEAD' state", git switch --detach does not. Was this > deliberate, on the assumption that if you pass --detach you know what > you are doing?
I'd say you are correct---one who passes "--detach" knows enough to want to be in the detached HEAD state and knows enough that the state is nothing to be worried about.