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

Re: git rebase behaviour changed?

From
Junio C Hamano <junkio@cox.net>
Date
Jan 17, 2006, 08:43 UTC
Message-ID
<7vvewjb5xz.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<46a038f90601170033y334d111fjed277fc787a2e523@mail.gmail.com>
Martin Langhoff <martin.langhoff@gmail.com> writes:
> GIT won't literally lose them,  someone could run git-fsck and fish
> out the dangling heads from the repo, and after a bit of spelunking
> recover them, but it's suddenly a really tricky operation.
"git-lost-found".

You are right. We will lose #1 and #2, (although the "already up to date" might catch some cases) and this _is_ dangerous. I need to do something about this soon.

Thanks for the discussion.
[Footnote]

*1* ... or #1 and #3 --- sorry, my "one of them picked up by upstream" scenario description was inconsistent in the previous message.

Previous: Martin LanghoffNext: Junio C Hamano
Message 8 of 9 in “git rebase behaviour changed?”
  1. Mike McCormackJan 17, 2006
  2. Junio C HamanoJan 17, 2006
  3. Mike McCormackJan 17, 2006
  4. Junio C HamanoJan 17, 2006
  5. Martin LanghoffJan 17, 2006
  6. Junio C HamanoJan 17, 2006
  7. Martin LanghoffJan 17, 2006
  8. Junio C HamanoJan 17, 2006
  9. Junio C HamanoJan 17, 2006

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.