From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: pull-request: bpf 2024-06-24
Date: Tue, 25 Jun 2024 07:13:14 -0700 [thread overview]
Message-ID: <20240625071314.00fdb459@kernel.org> (raw)
In-Reply-To: <c2119e37-4ce4-bf9b-61c2-1728c7c2b0ce@iogearbox.net>
On Tue, 25 Jun 2024 09:46:39 +0200 Daniel Borkmann wrote:
> On 6/25/24 3:41 AM, Jakub Kicinski wrote:
> > On Mon, 24 Jun 2024 14:43:30 +0200 Daniel Borkmann wrote:
> >> The following changes since commit 143492fce36161402fa2f45a0756de7ff69c366a:
> >>
> >> Merge branch '40GbE' of git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue (2024-06-14 19:05:38 -0700)
> >>
> >> are available in the Git repository at:
> >>
> >> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev
> >
> > Bot seems to not be responding, so: pulled, thanks!
> >
> > BTW was the ssh link intentional?
>
> Yes at least from what I read at users@k.o the recommendation / preference is
> to use the gitolite link so that you as kernel.org user do not get artificially
> throttled when pulling.
Hm. Wasn't there some suggestion for people to locally have a rule to
replace links if they want that? The SSH link is impossible for bots to
pull. I guess I could sprinkle regexps in all the bots but that sounds
like a pain. And TBH I've personally never experienced the throttling
issues K mentioned, so I see no upside :(
next prev parent reply other threads:[~2024-06-25 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 12:43 pull-request: bpf 2024-06-24 Daniel Borkmann
2024-06-25 1:41 ` Jakub Kicinski
2024-06-25 7:46 ` Daniel Borkmann
2024-06-25 14:13 ` Jakub Kicinski [this message]
2024-06-25 15:42 ` Daniel Borkmann
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=20240625071314.00fdb459@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.