git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Instructions concerning detached head lead to lost local changes

From
Junio C Hamano <junkio@cox.net>
Date
Feb 2, 2007, 07:44 UTC
Message-ID
<7vps8thulj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0702020206480.3021@xanadu.home>
Nicolas Pitre <nico@cam.org> writes:
Show 9 quoted lines
> It's just that moving around amongst thousands of commits to pin point a 
> particular commit might require some digging work.  This is why there 
> might be some value in a particular position and why there is an attempt 
> at protecting that "work".
>
> But since moving to another position while still remaining detached from 
> any branch has the same potential for losing the important position and 
> so without any kind of protection then it makes no sense to have such a 
> protection when moving back to a branch.
Thanks -- I'd agree.

Also I agree that "reflog on HEAD" is the right direction as it makes these 'protection' unnecessary. I've applied all your patches from today on the topic, along with Johannes's "log -g @{now}".

Previous: Nicolas Pitre
Message 9 of 9 in “Instructions concerning detached head lead to lost local changes”
  1. Carl WorthFeb 1, 2007
  2. Linus TorvaldsFeb 1, 2007
  3. Junio C HamanoFeb 2, 2007
  4. Carl WorthFeb 2, 2007
  5. Carl WorthFeb 2, 2007
  6. Nicolas PitreFeb 2, 2007
  7. Theodore TsoFeb 2, 2007
  8. Nicolas PitreFeb 2, 2007
  9. Junio C HamanoFeb 2, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.