public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/107655] New: [meta-bug] tracker bug for issues encountered in the texinfo-to-sphinx migration Date: Fri, 11 Nov 2022 22:46:13 +0000 [thread overview] Message-ID: <bug-107655-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107655 Bug ID: 107655 Summary: [meta-bug] tracker bug for issues encountered in the texinfo-to-sphinx migration Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: documentation, meta-bug Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Target Milestone: --- Creating this tracker bug in case it helps organize the various texinfo-to-sphinx migration issues.
next reply other threads:[~2022-11-11 22:46 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-11 22:46 dmalcolm at gcc dot gnu.org [this message] 2022-11-13 10:39 ` [Bug other/107655] " marxin at gcc dot gnu.org 2022-11-13 10:46 ` marxin at gcc dot gnu.org 2022-11-13 10:53 ` marxin at gcc dot gnu.org 2022-11-13 11:49 ` pinskia at gcc dot gnu.org 2022-11-13 12:05 ` pinskia at gcc dot gnu.org 2022-11-13 15:38 ` marxin at gcc dot gnu.org 2022-11-13 15:41 ` marxin at gcc dot gnu.org 2022-11-13 17:41 ` pinskia at gcc dot gnu.org 2022-11-14 8:43 ` marxin at gcc dot gnu.org 2022-11-14 8:43 ` marxin at gcc dot gnu.org 2022-11-14 8:43 ` marxin at gcc dot gnu.org 2022-11-14 8:43 ` marxin at gcc dot gnu.org 2022-11-14 8:43 ` marxin at gcc dot gnu.org 2022-11-14 8:44 ` marxin at gcc dot gnu.org 2022-11-14 8:44 ` marxin at gcc dot gnu.org 2022-11-14 8:44 ` marxin at gcc dot gnu.org 2022-11-14 8:44 ` marxin at gcc dot gnu.org 2022-11-14 8:44 ` marxin at gcc dot gnu.org 2022-11-14 8:45 ` marxin 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-107655-4@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: linkBe 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).