From: Noel Grandin <noelgrandin@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: filtering on git fetch?
Date: Wed, 17 Jun 2020 09:41:37 +0200 [thread overview]
Message-ID: <f6c1377f-6945-b04f-07cf-887c4b7c9f76@gmail.com> (raw)
Hi
Setup
(*) I'm fetching across a transatlantic link (RTT in the 300ms range on a good day)
(*) I'm fetching from a gerrit server
$ GIT_PACKET_TRACE=true git fetch
shows tons and tons of
09:39:43.355675 pkt-line.c:80 packet: fetch< 3a7ad7ee5d7daa0c93a80fbb32a677597d81ac75
refs/changes/00/9000/3
09:39:43.355684 pkt-line.c:80 packet: fetch< 6cacf1db5311f6b250ebaa12c71419a8ff9b747e
refs/changes/00/9000/meta
09:39:43.355693 pkt-line.c:80 packet: fetch< 849a43434a5ede9ce9b70da14231f34edb2593fb
refs/changes/00/90100/1
type stuff before it starts fetching the updates to master that I am interested in.
Is there any way to tell the remote git server that I'm only interested in a subset of stuff?
Thanks, Noel Grandin
next reply other threads:[~2020-06-17 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 7:41 Noel Grandin [this message]
2020-06-17 8:34 ` filtering on git fetch? Jeff King
2020-06-17 8:42 ` Noel Grandin
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=f6c1377f-6945-b04f-07cf-887c4b7c9f76@gmail.com \
--to=noelgrandin@gmail.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).