public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106899] Snapshots do not contain pre-generated man pages & info pages
Date: Sat, 19 Aug 2023 20:19:49 +0000 [thread overview]
Message-ID: <bug-106899-4-ajBjii9wdY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106899-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899
Mark Wielaard <mark at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at gcc dot gnu.org
--- Comment #6 from Mark Wielaard <mark at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> The resource issue is probably a non-issue these days
Yes, we have more hardware these these. Even a separate machine just to create
snapshots. Thanks to OSUOSL we now have https://snapshots.sourceware.org/ to
publish static artifacts from current git repos created in isolated containers.
It can be used as alternative to cron jobs on the main machine to generate
snapshots and documentation. The container files and build steps are defined
through the builder project.
We could do both. Have the current snapshots once a week. And have a full
"release snapshot" through snapshorts.sourceware.org whenever the sources
change (every hour) that regenerates all generated files (so we also know
whenever manual creation is broken).
next prev parent reply other threads:[~2023-08-19 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 2:54 [Bug other/106899] New: " sam at gentoo dot org
2022-09-10 3:00 ` [Bug other/106899] " pinskia at gcc dot gnu.org
2022-09-10 3:06 ` pinskia at gcc dot gnu.org
2022-09-10 3:15 ` sam at gentoo dot org
2022-09-10 3:43 ` pinskia at gcc dot gnu.org
2022-09-12 7:46 ` rguenth at gcc dot gnu.org
2023-08-19 20:19 ` mark at gcc dot gnu.org [this message]
2024-04-11 1:17 ` [Bug other/106899] Snapshots maybe should " pinskia at gcc dot gnu.org
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=bug-106899-4-ajBjii9wdY@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).