Re: [PATCH] Proof-of-concept patch to remember what the detached HEAD was

On Wed, 14 Oct 2009, Nicolas Pitre wrote:

On Wed, 14 Oct 2009, Daniel Barkalow wrote:

quoted

On Wed, 14 Oct 2009, Jay Soffian wrote:

quoted

$ 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?

I suppose; I don't know if that would be acceptable to the relevant users. 
It would certainly require script changes, but that's not an issue for 
1.7.0, presumably.

I personally normally use the order:

$ git checkout origin/master
(change stuff, test)
$ git checkout -b my-topic
$ git commit

So I only care about detaching, not committing while detached, and I'm not 
the right person to ask.

	-Daniel
*This .sig left intentionally blank*