public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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, 10 Sep 2022 03:06:06 +0000	[thread overview]
Message-ID: <bug-106899-4-g3uULXLR4h@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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
"Public releases and weekly snapshots of the development sources are also
available via HTTPS."

"Necessary to build GCC documentation during development because the generated
output files are not included in the repository. They are included in
releases."

From https://gcc.gnu.org/install/prerequisites.html


Also I suspect building the snapshot with the generated files will no longer be
considered a snapshot but a snap release instead. Since it is not exactly what
is in the git repo anymore.

  parent reply	other threads:[~2022-09-10  3:06 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 [this message]
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
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-g3uULXLR4h@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).