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

Re: Losing branches (whee, data loss)

From
JGJeff Garzik <jeff@garzik.org>
Date
May 16, 2007, 06:40 UTC
Message-ID
<464AA773.3090808@garzik.org>
In-Reply-To
<20070516061449.GA25273@artax.karlin.mff.cuni.cz>
Jan Hudec wrote:
> And does the .git/logs/refs/heads/upstream-fixes still exist?
Nope.
> If it does not, as last resort you'd have to git fsck --unreachable
> (this gives you all things that are not reachable from any ref), filter
> out only commit objects and than remember which one should have been on
> that branch after reading it's log, date and changes.

Yeah, that will probably recover it. I wound up digging the emails out of the trash bin, and applying them again.

	Jeff
Previous: Jan HudecNext: Junio C Hamano
Message 5 of 10 in “Losing branches (whee, data loss)”
  1. Jeff GarzikMay 16, 2007
  2. Lars HjemliMay 16, 2007
  3. Jeff GarzikMay 16, 2007
  4. Jan HudecMay 16, 2007
  5. Jeff GarzikMay 16, 2007
  6. Junio C HamanoMay 16, 2007
  7. Lars HjemliMay 16, 2007
  8. Junio C HamanoMay 16, 2007
  9. Junio C HamanoMay 16, 2007
  10. Jeff GarzikMay 16, 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.