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

Properties of trees referencing commit objects (mode 160000)?

From
Josh Triplett <josh@joshtriplett.org>
Date
Mar 19, 2016, 22:13 UTC
Message-ID
<20160319221348.GA5247@x>
I'm building some tools to track commit objects, and I'm thinking of
using submodule-style references to commit objects in tree objects (mode
160000) to do so.  I'm trying to figure out some of the properties of
that.

Can a commit object referenced that way live in the same repository, rather than some external repository?

Will git treat such a reference as keeping the commit object (and everything recursively referenced by it) live and reachable? If that commit object is only reachable by the tree, and not by following the parents of any commit directly referenced from refs/*, will git discard it as unreachable?

- Josh Triplett
Next: Jeff King
Message 1 of 9 in “Properties of trees referencing commit objects (mode 160000)?”
  1. Josh TriplettMar 19, 2016
  2. Jeff KingMar 20, 2016
  3. Josh TriplettMar 20, 2016
  4. Jeff KingMar 20, 2016
  5. Josh TriplettMar 20, 2016
  6. Jeff KingMar 21, 2016
  7. Josh TriplettMar 21, 2016
  8. Junio C HamanoMar 20, 2016
  9. Josh TriplettMar 20, 2016

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.