Re: [PATCH] Proof-of-concept patch to remember what the detached HEAD was
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 14, 2009, 20:42 UTC
- Message-ID
- <7v7huxbtbk.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <alpine.LFD.2.00.0910141616530.20122@xanadu.home>
Nicolas Pitre <nico@fluxnic.net> writes:
Show 14 quoted lines
> On Wed, 14 Oct 2009, Daniel Barkalow wrote: > >> On Wed, 14 Oct 2009, Jay Soffian wrote: >> >> > $ git commit -m "blah" >> > Cannot commit while not on any branch. Please use git commit -b <branch> to >> > specify the name of a new branch to commit to, or use git commit -f to >> > force a detached commit. >> >> The difference is that some experienced users depend on being able to >> commit while not on a branch, and want to not get a warning for every >> commit while not on a branch. > > I assume that the -f would silence any warning?
It won't help to alleviate my irritation if I need to give -f to each and every invocation of "git commit" while detached, though.