> Not heretical. How do you intend to switch branches now? Point .git/HEAD at the branch like usual. .git/HEAD would not be a symref *only* when on the unnamed temporary branch (which doesn't accept commits). > And how do you intend to record the starting point of git-seek to > which you want to return to? Te same way it's done now for git-seek or git-bisect: by copying the old HEAD to a temporary location like .git/head-name. > All leads back to .git/HEAD pointing to a branch (or whatever > you want to call it). In the usual case, yes it should. Any time you want to be able to develop on a branch, you need .git/HEAD pointing to a branch. You only make it point to a commit directly is when exploring the history with no intention of developing from it. (Note that you can easily change your mind with a simple "git checkout -b <branch>".) > And BTW, .git/HEAD is no symlink these days, but a symref. Yes, I'm sorry; I was just being lazy with my terminology. - : 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