[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240625071314.00fdb459@kernel.org>
Date: Tue, 25 Jun 2024 07:13:14 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com,
ast@...nel.org, andrii@...nel.org, martin.lau@...ux.dev,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: pull-request: bpf 2024-06-24
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@...olite.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 :(
Powered by blists - more mailing lists