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

On Tue, Nov 18, 2014 at 09:34:26AM +0900, Mike Hommey wrote:
> 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).

BTW, if it so happens that all the operations that were done end up
creating objects that already existed for some reason, checkpoint
doesn't do anything, which is fine for the pack and tags, but not
necessarily so for export-marks.

Mike

  parent reply	other threads:[~2014-11-18  2:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  0:34 Getting a commit sha1 from fast-import in a remote-helper Mike Hommey
2014-11-18  1:40 ` 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 [this message]
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=20141118022137.GA8418@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).