Nicolas Pitre <nico@xxxxxxxxxxx> writes: > On Wed, 14 Oct 2009, Junio C Hamano wrote: > >> Nicolas Pitre <nico@xxxxxxxxxxx> writes: >> >> > 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. > > Agreed. Presumably some expert mode config would imply -f > automatically. No, I do not want an expert mode. I can probably live with "per session" setting, that makes me decide to set or not set it when I detach, though. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html