git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: Getting a commit sha1 from fast-import in a remote-helper
Date: Tue, 18 Nov 2014 09:34:26 +0900	[thread overview]
Message-ID: <20141118003426.GA6528@glandium.org> (raw)

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

             reply	other threads:[~2014-11-18  0:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  0:34 Mike Hommey [this message]
2014-11-18  1:40 ` Getting a commit sha1 from fast-import in a remote-helper Jonathan Nieder
2014-11-18  2:31   ` Mike Hommey
2014-11-18  2:51     ` Jonathan Nieder
2014-11-18  3:11       ` Mike Hommey
2014-11-19  2:18         ` Mike Hommey
2014-11-19  2:21           ` Jonathan Nieder
2014-11-19  2:27             ` Mike Hommey
2014-11-19  2:36               ` Jonathan Nieder
2014-11-18  2:21 ` Mike Hommey
2014-11-18  2:35   ` Mike Hommey
2014-11-18  3:27     ` Jonathan Nieder
2014-11-18  4:17       ` Mike Hommey
2014-11-18  2:53   ` Jonathan Nieder
2014-11-18  3:14     ` Mike Hommey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141118003426.GA6528@glandium.org \
    --to=mh@glandium.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).