From: Jonathan Nieder <jrnieder@gmail.com>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org
Subject: Re: Getting a commit sha1 from fast-import in a remote-helper
Date: Mon, 17 Nov 2014 18:53:59 -0800 [thread overview]
Message-ID: <20141118025359.GI4336@google.com> (raw)
In-Reply-To: <20141118022137.GA8418@glandium.org>
Mike Hommey wrote:
> 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.
Does something like this help?
Do you have a short script that can demonstrate the failure?
Lazily,
Jonathan
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
diff --git i/fast-import.c w/fast-import.c
index d0bd285..c3d53c8 100644
--- i/fast-import.c
+++ w/fast-import.c
@@ -3088,12 +3088,11 @@ static void parse_ls(const char *p, struct branch *b)
static void checkpoint(void)
{
checkpoint_requested = 0;
- if (object_count) {
+ if (object_count)
cycle_packfile();
- dump_branches();
- dump_tags();
- dump_marks();
- }
+ dump_branches();
+ dump_tags();
+ dump_marks();
}
static void parse_checkpoint(void)
next prev parent reply other threads:[~2014-11-18 2:54 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
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 [this message]
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=20141118025359.GI4336@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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).