From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>, gitster@pobox.com
Subject: [PATCH v2 0/3] make packfile URIs work with transfer.fsckobjects
Date: Mon, 17 Aug 2020 12:48:17 -0700 [thread overview]
Message-ID: <cover.1597693540.git.jonathantanmy@google.com> (raw)
In-Reply-To: <20200814193234.3072139-1-jonathantanmy@google.com>
Thanks, Junio, for taking a look.
Differences from v1:
- Added 2 patches that document parts that Junio mentioned were
underdocumented [1]. I'm not sure about only_packfile, since it's
narrowly scoped (just an argument in a static function) but I've
included it anyway.
- Used <<-EOF instead of <<EOF.
[1] https://lore.kernel.org/git/xmqq8sehvw13.fsf@gitster.c.googlers.com/
Jonathan Tan (3):
(various): document from_promisor parameter
fetch-pack: document only_packfile in get_pack()
fetch-pack: make packfile URIs work with transfer.fsckobjects
fetch-pack.c | 6 ++++-
fetch-pack.h | 8 +++++++
remote-curl.c | 3 +++
t/t5702-protocol-v2.sh | 53 ++++++++++++++++++++++++++++++++++++++++++
transport.h | 3 +++
5 files changed, 72 insertions(+), 1 deletion(-)
--
2.28.0.220.ged08abb693-goog
next prev parent reply other threads:[~2020-08-17 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 19:32 [PATCH] fetch-pack: make packfile URIs work with transfer.fsckobjects Jonathan Tan
2020-08-14 19:59 ` Junio C Hamano
2020-08-17 19:48 ` Jonathan Tan [this message]
2020-08-17 19:48 ` [PATCH v2 1/3] (various): document from_promisor parameter Jonathan Tan
2020-08-17 19:48 ` [PATCH v2 2/3] fetch-pack: document only_packfile in get_pack() Jonathan Tan
2020-08-17 19:48 ` [PATCH v2 3/3] fetch-pack: make packfile URIs work with transfer.fsckobjects Jonathan Tan
2020-08-17 19:52 ` Eric Sunshine
2020-08-17 20:22 ` 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=cover.1597693540.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).