From: David Kastrup <dak@gnu.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.0.0-rc4
Date: Wed, 21 May 2014 06:25:24 +0200 [thread overview]
Message-ID: <87tx8jahcb.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <537bf50f27417_353e13c330846@nysa.notmuch> (Felipe Contreras's message of "Tue, 20 May 2014 19:36:31 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> Junio C Hamano wrote:
>
>> * The remote-helper interface to fast-import/fast-export via the
>> transport-helper has been tightened to avoid leaving the import
>> marks file from a failed/crashed run, as such a file that is out-of-
>> sync with reality confuses a later invocation of itself.
>
> Really? Where are the patches for that?
The following seems related:
commit 10e1feebb454d99eb6644cc53b94255f40e6fe9c
Author: Junio C Hamano <gitster@pobox.com>
Date: Wed May 14 12:06:35 2014 -0700
Revert "Merge branch 'fc/transport-helper-sync-error-fix'"
This reverts commit d508e4a8e2391ae2596403b6478d01cf3d5f928f,
reversing changes made to e42552135a2a396f37053a89f44952ea907870b2.
The author of the original topic says he broke the upcoming 2.0
release with something that relates to "synchronization crash
regression" while refusing to give further specifics, so this would
unfortunately be the safest option for the upcoming release.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
--
David Kastrup
next prev parent reply other threads:[~2014-05-21 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 0:24 [ANNOUNCE] Git v2.0.0-rc4 Junio C Hamano
2014-05-21 0:36 ` Felipe Contreras
2014-05-21 4:25 ` David Kastrup [this message]
2014-05-21 17:05 ` Junio C Hamano
2014-05-22 3:45 ` Felipe Contreras
2014-05-21 21:30 ` Richard Hansen
2014-05-21 21:48 ` Junio C Hamano
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=87tx8jahcb.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@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