From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Tan <jonathantanmy@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Fail early when partial clone prefetch fails
Date: Thu, 29 Sep 2022 13:15:14 -0700 [thread overview]
Message-ID: <xmqqczbendil.fsf@gitster.g> (raw)
In-Reply-To: <cover.1664316642.git.jonathantanmy@google.com> (Jonathan Tan's message of "Tue, 27 Sep 2022 15:12:28 -0700")
Jonathan Tan <jonathantanmy@google.com> writes:
> This fixes something we noticed at $DAYJOB, when a partial clone
> prefetch intermittently fails but all subsequent fetches work. More
> details are in patch 2's commit message.
>
> Jonathan Tan (2):
> promisor-remote: remove a return value
> promisor-remote: die upon failing fetch
>
> object-file.c | 4 ----
> promisor-remote.c | 23 ++++++++++++++---------
> promisor-remote.h | 11 +++++------
> 3 files changed, 19 insertions(+), 19 deletions(-)
No changes to t/ directory?
next prev parent reply other threads:[~2022-09-29 20:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 22:12 [PATCH 0/2] Fail early when partial clone prefetch fails Jonathan Tan
2022-09-27 22:12 ` [PATCH 1/2] promisor-remote: remove a return value Jonathan Tan
2022-09-29 19:23 ` Junio C Hamano
2022-09-30 22:02 ` Jonathan Tan
2022-09-27 22:12 ` [PATCH 2/2] promisor-remote: die upon failing fetch Jonathan Tan
2022-09-28 17:43 ` Glen Choo
2022-09-30 22:10 ` Jonathan Tan
2022-09-29 20:14 ` Junio C Hamano
2022-09-29 20:15 ` Junio C Hamano [this message]
2022-09-30 21:50 ` [PATCH 0/2] Fail early when partial clone prefetch fails Jonathan Tan
2022-09-30 22:17 ` Junio C Hamano
2022-10-04 21:13 ` [PATCH v2 " Jonathan Tan
2022-10-04 21:13 ` [PATCH v2 1/2] promisor-remote: remove a return value Jonathan Tan
2022-10-04 21:13 ` [PATCH v2 2/2] promisor-remote: die upon failing fetch Jonathan Tan
2022-10-05 18:09 ` [PATCH v2 0/2] Fail early when partial clone prefetch fails 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=xmqqczbendil.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.