From: Eli Schwartz via Gdb <gdb@sourceware.org>
To: "Tomasz Kłoczko" <kloczko.tomasz@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 19:26:50 -0500 [thread overview]
Message-ID: <0d82add5-2d61-4901-9232-a1317b6a0827@gmail.com> (raw)
In-Reply-To: <CABB28CwU=fKV--mJBFWqBA5mEzJXdqahWR=P7y_ktLbRP8TFPw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1771 bytes --]
On 2/25/24 4:50 PM, Tomasz Kłoczko wrote:
> 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.
No.
I'm suggesting you cache all 4444 of them. When your cache starts to get
near the limits of its disk space, start evicting the least recently
used ones.
This is standard caching technology.
Thanks.
> 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?🤔
I truly have no idea why you think anyone has suggested you acquire an
account on builder.sourceware.org, as that has never even tangentially
been suggested.
Perhaps you should re-read the thread?
--
Eli Schwartz
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-26 0:27 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
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 [this message]
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=0d82add5-2d61-4901-9232-a1317b6a0827@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