From: Jonathan Tan <jonathantanmy@google.com>
To: peff@peff.net
Cc: git@vger.kernel.org, jonathantanmy@google.com
Subject: Re: [PATCH 0/7] some fetch reachability-error fixes
Date: Mon, 15 Apr 2019 14:06:45 -0700 [thread overview]
Message-ID: <20190415210645.100478-1-jonathantanmy@google.com> (raw)
In-Reply-To: <20190413055127.GA32340@sigill.intra.peff.net>
> [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
All these look good to me. Thanks for catching the issue that you fixed
in patch 4.
prev parent reply other threads:[~2019-04-15 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 5:51 [PATCH 0/7] some fetch reachability-error fixes Jeff King
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 ` Jonathan Tan [this message]
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=20190415210645.100478-1-jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).