From: "Frank Ch. Eigler" <fche@redhat.com>
To: brobecker@adacore.com, gdb@sourceware.org
Subject: value of gdbadmin effort to create gdb daily/weekly source tarballs
Date: Mon, 15 Apr 2024 10:34:28 -0400 [thread overview]
Message-ID: <20240415143428.GA24230@redhat.com> (raw)
Hi -
Observing regular system activity on sourceware, the gdbadmin cron
jobs to create the https://sourceware.org/pub/gdb/snapshots/ struck me
as something that perhaps is no longer that useful. With git-archive
being able to immediately generate tarballs of any version, with git
diffs producing the deltas, is there any utility at all in still
producing these tarballs?
Would you like me to check logs as to how many accesses to this have
taken place? (A very rough brief search indicated 99%+ were bots like
search engines and ai ingesters.)
- FChE
next reply other threads:[~2024-04-15 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:34 Frank Ch. Eigler [this message]
2024-04-15 17:48 ` Joel Brobecker
2024-04-15 18:14 ` Mark Wielaard
2024-04-15 18:26 ` Joel Brobecker
2024-05-24 23:17 ` Mark Wielaard
2024-04-15 18:28 ` Frank Ch. Eigler
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=20240415143428.GA24230@redhat.com \
--to=fche@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).