On Wed, 31 Jan 2007, Jakub Narebski wrote: > I'd like to have some configuration option to make git more careful > and prohibit commiting in detached HEAD state (the default being that > you can commit on top of detached HEAD). More secure but less powerfull. And what is the purpose of such an artificial annoyance that no one will turn on on purpose? You have to _realize_ that there is nothing wrong with such commits. Merely having a config option to prohibit them not only is senseless technically but it also send the wrong message to users. > > By the same argument, the original checkout of a non-branch is also not > > the place for a warning; by the time you commit and then do a checkout > > to switch away from the new commit, that original checkout may be a > > distant memory. > > But the initial checkout of a non-branch is place where we can notify > user that he does something unexpected / unusual. Though I think that > single-line warning would be enough... There is a balance problem there. Too large a message might be annoying but a too short one might not convey enough information not to be yet more confusing. Nicolas - 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