On 30/01/2010 06:03, Junio C Hamano wrote: >Nicolas Pitre <nico@xxxxxxxxxxx> writes: >>First, I'm afraid that "Checking out commit 'foobar'" might be confusing >>as this may happen through either a remote branch, a tag, or any random >>commit. It seems to me that "Checking out 'v2.5'" is less confusing >>than "Checking out commit 'v2.5'". But that's a minor detail and >>probably a personal preference. ... >>To the contrary: this "detached HEAD" is exactly what you need if you >>want to relate to any documentation or perform a search for more >>information. Like it or not, this detached HEAD term is exactly what >>this Git concept is all about and how it is designated everywhere. The >>sooner Git users see and learn about it the better. >As I am not good at keeping track of different proposals to change this >word here and that word there, I expect this will probably need at least >few rotations of earth to get input from people in different timezones, >and I think this is post 1.7.0 item anyway, I'll queue the attached draft >in 'pu' and keep it there, to make it easier for others to tweak the >message. Would it be a safe assumption to describe a 'detached HEAD' state as being synonymous with a (local) personal scratchpad or temporary workspace based on and from the original committed object? If this assumption is correct, then maybe this notion of a scratchpad may be more intuitive and conceptual to new users without getting bogged down with the necessary semantics of the terms used, but can also preserve references to 'detached HEAD' in the documentation for a fuller explanation. A scratchpad or temporary workspace description alludes to its semi permanent nature, and can warn that the subsequent commits may be lost through aging and garbage collection until the user "commits" to saving their progress through the creation a new branch, and thereby making them permanent. I must say the explanations presented in this thread have shed some light on what is on the face of it a common trap that leaves new users wondering "What happened to my work!" and I thank you all. Steve -- 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