Matthias Lederhofer <matled@xxxxxxx> writes: >> * Coming back to an attached state can lose the detached HEAD, so >> I get warned and stopped. >> >> [git.git]$ git checkout master >> You are not on any branch and switching to branch 'master' >> may lose your changes. At this point, you can do one of two things: >> (1) Decide it is Ok and say 'git checkout -f master'; >> (2) Start a new branch from the current commit, by saying >> 'git checkout -b <branch-name>'. >> Leaving your HEAD detached; not switching to branch 'master'. > > I think these two are too long, after a few times one knows exactly > what to do and all this text is not necessary anymore. I doubt adding a per-repo or per-user configuration would be worth it. The original hope was after a few times one would know to use either -f or -b depending on what he wants, and would not run plain vanilla branch switching "git checkout master". Then one does not even have to see this message, not just the last "instruction" lines but "You are not on any branch" part. - 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