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

Getting a commit sha1 from fast-import in a remote-helper

From
Mike Hommey <mh@glandium.org>
Date
Nov 18, 2014, 00:34 UTC
Message-ID
<20141118003426.GA6528@glandium.org>
Hi,
For some reason, I need to know the sha1 corresponding to some marks
I'm putting in a fast-import stream. Unfortunately, this does not appear
to be possible.
- I'd rather not require a checkpoint to export marks each time I need
  such a sha1, and I'd rather not do that work that requires them after
  all the marks have been created (although currently, I'm forced to).
- fast-import's cat-blob only allows to cat blobs, which, well, is kind
  of in its name; how about adding an equivalent to the git-cat-file
  command?
- fast-import's `ls` command documentation about its output format
  mentions that the output may contain commits, so I tried the trick of
  creating a tree with commits, but fast-import then fails with:
    fatal: Not a blob (actually a commit)
  which I totally understand, but then I wonder why the documentation
  mentions it and how one would get a tree containing references to
  commits. I guess the documentation should be fixed.

So, while there's a possible solution with an equivalent to the git-cat-file command if that'd be accepted, that's also overkill for my need, which is to simply get the sha1 corresponding to a mark. Would you consider a patch adding a command that allows such a resolution?

Cheers,
Mike
Next: Jonathan Nieder
Message 1 of 15 in “Getting a commit sha1 from fast-import in a remote-helper”
  1. Mike HommeyNov 18, 2014
  2. Jonathan NiederNov 18, 2014
  3. Mike HommeyNov 18, 2014
  4. Jonathan NiederNov 18, 2014
  5. Mike HommeyNov 18, 2014
  6. Mike HommeyNov 19, 2014
  7. Jonathan NiederNov 19, 2014
  8. Mike HommeyNov 19, 2014
  9. Jonathan NiederNov 19, 2014
  10. Mike HommeyNov 18, 2014
  11. Mike HommeyNov 18, 2014
  12. Jonathan NiederNov 18, 2014
  13. Mike HommeyNov 18, 2014
  14. Jonathan NiederNov 18, 2014
  15. Mike HommeyNov 18, 2014

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.