From: Noel Grandin <noelgrandin@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>
Subject: Re: filtering on git fetch?
Date: Wed, 17 Jun 2020 10:42:24 +0200 [thread overview]
Message-ID: <e3ec6fec-b872-b548-0eb0-d085ca36c99b@gmail.com> (raw)
In-Reply-To: <20200617083423.GA695303@coredump.intra.peff.net>
On 2020/06/17 10:34 am, Jeff King wrote:
>
> The ref advertisement in the v0 protocol is unconditional and always
> complete. In v2, the client is able to specify which parts of the
> namespace it cares about.
Thanks
I tried (BTW my version is 2.26.2)
$ GIT_TRACE_PACKET=1 git -c protocol.version=2 pull -r
and the first few lines look like
10:35:59.323490 pkt-line.c:80 packet: fetch< ad0351b84926075297fb74abbe9b31a0455782af HEAD\0
include-tag multi_ack_detailed multi_ack o
fs-delta side-band side-band-64k thin-pack no-progress shallow agent=JGit/5.3.7.202002110540-r symref=HEAD:refs/heads/master
10:35:59.323583 pkt-line.c:80 packet: fetch< baeb5486c43d39b063371f91cfaae8efc2c8700b
refs/changes/00/1000/1
10:35:59.323592 pkt-line.c:80 packet: fetch< c5fb3d3f110f652e3c4b3920f71b7f77c227028e
refs/changes/00/1000/meta
10:35:59.323597 pkt-line.c:80 packet: fetch< dfbfb3c4d4cc7d7f519c197ef5cfa250c30b584b
refs/changes/00/10000/1
10:35:59.323602 pkt-line.c:80 packet: fetch< 5955e7d66d9b0e87f93fd9746a85bff132da9794
refs/changes/00/10000/2
10:35:59.323608 pkt-line.c:80 packet: fetch< ae3baacef7926d9ce9ca4786176f404b7cf78cc1
refs/changes/00/10000/meta
Is there something else I need to do on the client-side to make this work?
Noting that the git server at gerrit.libreoffice.org might be a JGit based thing, so maybe I need to log a feature
request there to support v2?
next prev parent reply other threads:[~2020-06-17 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 7:41 filtering on git fetch? Noel Grandin
2020-06-17 8:34 ` Jeff King
2020-06-17 8:42 ` Noel Grandin [this message]
2020-06-17 11:32 ` Jeff King
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=e3ec6fec-b872-b548-0eb0-d085ca36c99b@gmail.com \
--to=noelgrandin@gmail.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.
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).