Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Tomasz Kłoczko via Gdb" <gdb@sourceware.org>
To: Eli Schwartz <eschwartz93@gmail.com>
Cc: Mark Wielaard <mark@klomp.org>, Sam James <sam@gentoo.org>,
	gdb@sourceware.org
Subject: Re: gdb and ancient GNU autotools
Date: Sun, 25 Feb 2024 21:50:19 +0000	[thread overview]
Message-ID: <CABB28CwU=fKV--mJBFWqBA5mEzJXdqahWR=P7y_ktLbRP8TFPw@mail.gmail.com> (raw)
In-Reply-To: <5e663511-557e-43ee-9c96-6591041d8587@gmail.com>

On Sun, 25 Feb 2024 at 21:19, Eli Schwartz <eschwartz93@gmail.com> wrote:
[..]

> I think it's not entirely unreasonable for a project to internally place
> its own demands on its own resources, with the knowledge of how much it
> has in the way of resources...
>

For some reason LITERALLY only ONE git repo is treating that as DEMAND.
No, I'm pointing to an INCORRECT/UNREALISTIC/causing some real issues on
client side web server settings.

> But yes, having a cache certainly helps.
>
> Rather, it is "having a cache is basic politeness unto others"


So you suggest that I should start caching ..

[tkloczko@pers-jacek SPECS]$ grep VCS:.*https://sourceware.org/git *spec |
wc -l
8

of 4444 git repos because some wannabe-webmaster added a throttling module
in the web server setup when NO ONE ELSE ANYWHERE is using such settings?
Really?🤔
If "yes" I have no more questions.

[..]

> Refusing to use a cache is called executing a DDoS campaign.
>

In DDoS acronym first D stands for DISTRIBUTED.
I'm using a SINGLE source IP.
Reaching the throttling level is not equal to DENIAL of service. So that is
the second D.
3rd .. do you really want to name ~0.5 req/s as realistic/justificable
setup?
How many people here are using web server reqs throttling and how many
amongst them are using so LOW values?
NONE?🤔
.. THREE misunderstandings/mistakes in ONE sentence.

Thank you for suggestions of using some public buildbots on which I have no
physical control.
Even if I'll be using those buildbots (which I'm not going to waste my time
because I have now WORKING build infra) execution of the same build
procedure will cause the SAME RESULT. Do you see that now?🤔

Nevertheless I have enough HW resources.
This off-topic part has NOTHING to do with using throttling settings in ONE
cgit web frontend is YET another mistake/misunderstanding.
As the old saying goes .. "the road to hell is paved with good advice".

One more time: please focus on gdb and issues related to its build
automation.

kloczek

  reply	other threads:[~2024-02-25 21:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 16:28 Tomasz Kłoczko via Gdb
2024-02-24 16:51 ` Sam James via Gdb
2024-02-24 17:15   ` Tomasz Kłoczko via Gdb
2024-02-24 17:21     ` Sam James via Gdb
2024-02-24 18:30       ` Tomasz Kłoczko via Gdb
2024-02-24 19:31         ` Mark Wielaard
2024-02-25  0:22           ` Tomasz Kłoczko via Gdb
2024-02-25  7:56             ` Mark Wielaard
2024-02-25  8:05             ` Eli Schwartz via Gdb
2024-02-25 10:40               ` Mark Wielaard
2024-02-25 21:19                 ` Eli Schwartz via Gdb
2024-02-25 21:50                   ` Tomasz Kłoczko via Gdb [this message]
2024-02-25 22:20                     ` Andreas Schwab
2024-02-25 23:32                     ` Mark Wielaard
2024-02-26  0:29                       ` Tomasz Kłoczko via Gdb
2024-02-26  0:46                         ` Eli Schwartz via Gdb
2024-02-26  0:55                           ` Tomasz Kłoczko via Gdb
2024-02-26 11:44                         ` Mark Wielaard
2024-02-26 12:13                           ` Tomasz Kłoczko via Gdb
2024-02-26  0:26                     ` Eli Schwartz via Gdb
2024-02-27 15:25         ` Tom Tromey
2024-02-27 16:37         ` Simon Marchi via Gdb
2024-02-27 17:33           ` Joseph Myers via Gdb
2024-02-27 17:42             ` Tom Tromey
2024-02-27 20:44             ` Tomasz Kłoczko via Gdb
2024-02-27 20:57               ` Tomasz Kłoczko via Gdb
2024-02-27 20:59               ` Sam James via Gdb
2024-02-26  0:58 ` Andrew Pinski via Gdb
2024-02-27 15:27   ` Tom Tromey

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='CABB28CwU=fKV--mJBFWqBA5mEzJXdqahWR=P7y_ktLbRP8TFPw@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=eschwartz93@gmail.com \
    --cc=kloczko.tomasz@gmail.com \
    --cc=mark@klomp.org \
    --cc=sam@gentoo.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