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

Where'd my GIT tree go?

From
TLTony Luck <tony.luck@gmail.com>
Date
Jul 7, 2005, 03:23 UTC
Message-ID
<12c511ca0507062023291a098e@mail.gmail.com>

http://www.kernel.org/git has stopped showing my linux-2.6 tree (the "to Linus" one, my "test-2.6" tree is still there).

This is probably my fault ... but I'm not sure exactly why.

Here's what I did. Last Thursday I applied a set of patches ... and my "apply" script choked on one of them. Some casual inspection convinced me that the changes had been applied, and I pushed the tree up to kernel.org.

But I was wrong, the 2nd out od a series of six was all messed up. And I'd applied a couple more patches on top of that. Since none of this had been pulled by Linus, I thought I'd clean it up and apologise to anyone who had pulled from my tree.

So I backed HEAD up to the last good commit. Re-applied the changes with a fixed version of the script, and then expected to find some detritus from the first application in .git/objects. But "git-fsck-cache --unreachable ..." only complained about the 2.6.11 tag/tree. Odd.

Then I pushed up to master.kernel.org ... and an hour later when the mirrors did their thing, git-web stopped showing my tree.

HEAD is still a symlink to refs/heads/master. And that has the SHA1 of my most recent commit ... which is present in .git/objects.

So what's wrong???
-Tony
Next: Jon Seymour
Message 1 of 4 in “Where'd my GIT tree go?”
  1. Tony LuckJul 7, 2005
  2. Jon SeymourJul 7, 2005
  3. Tony LuckJul 7, 2005
  4. Thomas GleixnerJul 7, 2005

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.