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

Branches and all commits

From
JNJon Nelson <jnelson-git@jamponi.net>
Date
Dec 19, 2005, 15:15 UTC
Message-ID
<Pine.LNX.4.63.0512190908140.6812@gheavc.wnzcbav.cig>

Should *all* commits be reachable via at least one branch? I ran into a situation this weekend that has me a little confused. I had performed a number of commits and such and I noticed that the author and committer info had suboptimal values. A bit of searching led me to a comment made by Linus that basically said "go hack git-convert-objects", which I did. After performing git-convert-objects on every commit object in .git/refs/heads and the requisite pruning, etc... just about everything looked fine. However, I still had a long series of commits that contained the wrong information. Further inspection makes it appear as though these commits are not reachable via any branch, although they are /all/ reachable via a series of tags. I worked around the problem by further modifying git-convert-objects to also understand tags (at least the basic ones I've got) and that's all taken care of, but the question remains: should *all* commit objects be reachable by at least one branch?

-- Jon Nelson <jnelson-git@jamponi.net>

Next: Andreas Ericsson
Message 1 of 6 in “Branches and all commits”
  1. Jon NelsonDec 19, 2005
  2. Andreas EricssonDec 19, 2005
  3. Jon NelsonDec 19, 2005
  4. Andreas EricssonDec 19, 2005
  5. Jon NelsonDec 19, 2005
  6. Andreas EricssonDec 19, 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.