From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH 0/2] Last big GIT_TEST_PROTOCOL_VERSION=2 fix, hopefully
Date: Mon, 25 Mar 2019 13:43:21 -0700 [thread overview]
Message-ID: <cover.1553546216.git.jonathantanmy@google.com> (raw)
This is built on master+jt/test-protocol-version, but should apply
cleanly to master.
After [1] and this patch set, there is only one more small thing to fix
or mark GIT_TEST_PROTOCOL_VERSION=0 at master+jt/test-protocol-version.
This is very similar to [2], which was neither reviewed nor merged,
perhaps because I had another patch [3] that I declared to supersede [2]
and that was merged as bd0b42aed3 ("fetch-pack: do not take shallow lock
unnecessarily", 2019-01-10). But it turns out that [3] was not enough to
make all tests pass with GIT_TEST_PROTOCOL_VERSION=2, hence this patch
set.
[1] https://public-inbox.org/git/20190322190139.151189-1-jonathantanmy@google.com/
[2] https://public-inbox.org/git/20181220195349.92214-1-jonathantanmy@google.com/
[3] https://public-inbox.org/git/20190110193645.34080-1-jonathantanmy@google.com/
Jonathan Tan (2):
fetch-pack: call prepare_shallow_info only if v0
fetch-pack: respect --no-update-shallow in v2
commit.h | 4 ++++
fetch-pack.c | 54 +++++++++++++++++++++++++++++++++++++++++-----------
2 files changed, 47 insertions(+), 11 deletions(-)
--
2.21.0.155.ge902e9bcae.dirty
next reply other threads:[~2019-03-25 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 20:43 Jonathan Tan [this message]
2019-03-25 20:43 ` [PATCH 1/2] fetch-pack: call prepare_shallow_info only if v0 Jonathan Tan
2019-03-26 5:00 ` Jeff King
2019-03-25 20:43 ` [PATCH 2/2] fetch-pack: respect --no-update-shallow in v2 Jonathan Tan
2019-03-26 5:20 ` Jeff King
2019-03-26 10:14 ` Duy Nguyen
2019-03-26 15:18 ` Jeff King
2019-03-26 15:39 ` Duy Nguyen
2019-03-26 17:37 ` Jonathan Tan
2019-03-26 18:18 ` Jeff King
2019-03-26 17:53 ` [PATCH v2 0/2] Last big GIT_TEST_PROTOCOL_VERSION=2 fix, hopefully Jonathan Tan
2019-03-26 17:53 ` [PATCH v2 1/2] fetch-pack: call prepare_shallow_info only if v0 Jonathan Tan
2019-03-26 17:53 ` [PATCH v2 2/2] fetch-pack: respect --no-update-shallow in v2 Jonathan Tan
2019-03-26 18:23 ` Jeff King
2019-03-26 18:20 ` [PATCH v2 0/2] Last big GIT_TEST_PROTOCOL_VERSION=2 fix, hopefully Jeff King
2019-03-26 19:31 ` [PATCH v3 " Jonathan Tan
2019-03-26 19:31 ` [PATCH v3 1/2] fetch-pack: call prepare_shallow_info only if v0 Jonathan Tan
2019-03-26 19:31 ` [PATCH v3 2/2] fetch-pack: respect --no-update-shallow in v2 Jonathan Tan
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=cover.1553546216.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--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).