From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Andrew Pinski <pinskia@gmail.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Revert Sphinx documentation [Was: Issues with Sphinx]
Date: Mon, 14 Nov 2022 14:06:26 +0100 (CET) [thread overview]
Message-ID: <47e82606-c8ee-bd85-d1d3-b685f0121047@pfeifer.com> (raw)
In-Reply-To: <e534170c-dab4-6498-ac54-f767414598a5@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Mon, 14 Nov 2022, Martin Liška wrote:
> The situation with the Sphinx migration went out of control. The TODO
> list overwhelmed me and there are road-blocks that can't be easily fixed
> with what Sphinx currently supports.
This migration was/is a huge and complex undertaking, and you have been
patiently chipping away at obstacle after obstacle.
So while it probably is disappointing it did not go through this time,
you made a lot of progress and important contributions - and we all
learned quite a bit more, also in terms of (not so obvious) requirements,
dependencies, and road blocks left which you summarized.
Timing was tricky for me being on the road last week and I am definitely
committed to keep helping with this transition. Maybe soon after we are in
stage 1 again?
And would it make sense to convert at least our installation docs and
https://gcc.gnu.org/install/ for the GCC 13 release?
Gerald
next prev parent reply other threads:[~2022-11-14 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+=Sn1m=F6JVszrTFS_v=rfC7nrO=X5pSbgestxtPr___QGQuA@mail.gmail.com>
2022-11-14 2:49 ` Martin Liška
2022-11-14 8:38 ` Martin Liška
2022-11-14 9:24 ` Jonathan Wakely
2022-11-14 22:26 ` Gerald Pfeifer
2022-11-14 13:06 ` Gerald Pfeifer [this message]
2022-11-15 10:05 ` Martin Liška
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=47e82606-c8ee-bd85-d1d3-b685f0121047@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=pinskia@gmail.com \
/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).