From: Joel Brobecker <brobecker@adacore.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
gdb@sourceware.org
Subject: Re: value of gdbadmin effort to create gdb daily/weekly source tarballs
Date: Mon, 15 Apr 2024 11:26:21 -0700 [thread overview]
Message-ID: <Zh1xTWMmUlL+Wf1n@adacore.com> (raw)
In-Reply-To: <20240415181447.GX1292@gnu.wildebeest.org>
> Other projects like glibc, valgrind, libabigail, etc. have moved their
> snapshots builds to http://snapshots.sourceware.org/ which creates a
https?
> snapshot build and creates documentation from current git. This makes
> sure the release processes/scripts keep working. And it has caught
> release issues early (which often don't occur during a normal
> developer build). Since this is part of the normal
> builder.sourceware.org infrastructure it also provides better
> visibility.
FWIW, that would definitely work for me. I do not have the time
to work on that, though :-(.
--
Joel
next prev parent reply other threads:[~2024-04-15 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:34 Frank Ch. Eigler
2024-04-15 17:48 ` Joel Brobecker
2024-04-15 18:14 ` Mark Wielaard
2024-04-15 18:26 ` Joel Brobecker [this message]
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=Zh1xTWMmUlL+Wf1n@adacore.com \
--to=brobecker@adacore.com \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=mark@klomp.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).