From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH 0/7] some fetch reachability-error fixes
Date: Sat, 13 Apr 2019 01:51:28 -0400 [thread overview]
Message-ID: <20190413055127.GA32340@sigill.intra.peff.net> (raw)
This series fixes a few minor bugs around clients trying to fetch
unreachable commits, along with a few associated cleanups.
There's a minor conflict in t5516 when merging with next, since that
adds GIT_TEST_PROTOCOL_VERSION, causing a few textual conflicts. The
resolution should be fairly clear.
Where appropriate, I took GIT_TEST_PROTOCOL_VERSION into account so that
after merging with next, all tests should still pass even with it set to
"2" (well, all the tests that do not already fail on vanilla 'next' with
that setting).
[1/7]: t5516: drop ok=sigpipe from unreachable-want tests
[2/7]: t5530: check protocol response for "not our ref"
[3/7]: upload-pack: send ERR packet for non-tip objects
[4/7]: pkt-line: prepare buffer before handling ERR packets
[5/7]: fetch: use free_refs()
[6/7]: remote.c: make singular free_ref() public
[7/7]: fetch: do not consider peeled tags as advertised tips
fetch-pack.c | 16 +++++++++-------
pkt-line.c | 9 +++++----
remote.c | 6 +++---
remote.h | 4 +++-
t/t5516-fetch-push.sh | 18 +++++++++++++++---
t/t5530-upload-pack-error.sh | 18 +++++++++++++++---
upload-pack.c | 11 ++++++++---
7 files changed, 58 insertions(+), 24 deletions(-)
-Peff
next reply other threads:[~2019-04-13 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 5:51 Jeff King [this message]
2019-04-13 5:52 ` [PATCH 1/7] t5516: drop ok=sigpipe from unreachable-want tests Jeff King
2019-04-13 5:53 ` [PATCH 2/7] t5530: check protocol response for "not our ref" Jeff King
2019-04-13 5:53 ` [PATCH 3/7] upload-pack: send ERR packet for non-tip objects Jeff King
2019-04-13 5:54 ` [PATCH 4/7] pkt-line: prepare buffer before handling ERR packets Jeff King
2019-04-13 5:54 ` [PATCH 5/7] fetch: use free_refs() Jeff King
2019-04-13 5:54 ` [PATCH 6/7] remote.c: make singular free_ref() public Jeff King
2019-04-13 5:57 ` [PATCH 7/7] fetch: do not consider peeled tags as advertised tips Jeff King
2019-04-15 21:06 ` [PATCH 0/7] some fetch reachability-error fixes 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190413055127.GA32340@sigill.intra.peff.net \
--to=peff@peff.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).