From: Mark Wielaard <mark@klomp.org>
To: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Cc: Eli Schwartz <eschwartz93@gmail.com>, Sam James <sam@gentoo.org>,
gdb@sourceware.org
Subject: Re: gdb and ancient GNU autotools
Date: Mon, 26 Feb 2024 00:32:08 +0100 [thread overview]
Message-ID: <20240225233208.GD15517@gnu.wildebeest.org> (raw)
In-Reply-To: <CABB28CwU=fKV--mJBFWqBA5mEzJXdqahWR=P7y_ktLbRP8TFPw@mail.gmail.com>
Hi Tomasz,
On Sun, Feb 25, 2024 at 09:50:19PM +0000, Tomasz Kłoczko wrote:
> On Sun, 25 Feb 2024 at 21:19, Eli Schwartz <eschwartz93@gmail.com> wrote:
> 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?
Please stop being so disrespectful towards people who are trying to
help you. You are complaining about being throttled and if you really
are, then we would like to resolve that. Because we don't want normal
users to be throttled. We can give you some suggestions on how to
prevent that if you clearly explain which resources on sourceware.org
you are fetching.
You seem to be using the gitweb interface to fetching files or
diffs. If so, and because gitweb is known to be not very resource
efficient, you really should switch to using cgit.
But we are really speculating here. It isn't really clear what you are
doing and what issues you are seeing.
Offlist you said that you didn't really got throttled because of those
8 packages you have that are hosted on sourceware none of them need
many patches in the first place. So it isn't clear to me if we are
actually discussing a real issue or if you are just worried that you
could have an issue in theory.
Cheers,
Mark
next prev parent reply other threads:[~2024-02-25 23:32 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 [this message]
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=20240225233208.GD15517@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=eschwartz93@gmail.com \
--cc=gdb@sourceware.org \
--cc=kloczko.tomasz@gmail.com \
--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