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

Pushing and fetching sha1s directly

From
Finn Arne Gangstad <finnag@pvv.org>
Date
Dec 22, 2007, 21:13 UTC
Message-ID
<20071222211308.GA27281@pvv.org>

Currently there seems to be no way of pusing a sha1 directly, or to fetch a sha1 directly. When working with submodules, it is convenient to be able to work with detached HEADs, so it would be good if this could be supported also by fetch and push.

What would be a resonable syntax for this? I'm thinking something like git fetch --sha1 <repository> <sha1> git push --sha1 <repository> <sha1>

Where <sha1> could really be a <commit> I guess, but the option name "--commit" seems wrong somehow. Another option is to extend refspecs so sha1s can be allowed in there directly, so this would just work:

git fetch <repository> <sha1>
What do you prefer?
- Finn Arne
Next: Junio C Hamano
Message 1 of 3 in “Pushing and fetching sha1s directly”
  1. Finn Arne GangstadDec 22, 2007
  2. Junio C HamanoDec 22, 2007
  3. Johannes SchindelinDec 23, 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.