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

FEATURE/QUESTION: git fetch only commit objects, but not tree/file objects

From
Antonio Russo <aerusso@aerusso.net>
Date
Nov 29, 2024, 16:24 UTC
Message-ID
<c99248d4-777f-461b-b4ab-4cc8df3f09a3@aerusso.net>
Hello everyone,

Sometimes I'd like to investigate the commit history of a (large) git repository, but I don't actually (yet) care about the actual files in the repository. I know about shallow clones, but it covers kind of the opposite problem: a person may just want the files, but not the history.

1. Is there a way to download only the git commit objects, and not the
corresponding tree (or file) blobs?
2. Is this a use case that anyone else cares about?  I suppose a ton of code
assumes it can follow any references, so implementing this as a feature means a
ton of code would need to be adapted to handle the reference-not-locally-present
case.  Maybe it might be interesting, but would make the git code-base way too
complicated?

I don't really know what keywords to look for, and man git-fetch did not superficially seem to answer this, so I apologize if I wasn't able to find this feature in the documentation.

Best, Antonio

Next: Junio C Hamano
Message 1 of 2 in “FEATURE/QUESTION: git fetch only commit objects, but not tree/file objects”
  1. Antonio RussoNov 29, 2024
  2. Junio C HamanoDec 1, 2024

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.