public inbox for
 help / color / mirror / Atom feed
From: "Martin Liška" <>
To: Gerald Pfeifer <>
Cc: Andrew Pinski <>,,
Subject: Re: Revert Sphinx documentation [Was: Issues with Sphinx]
Date: Tue, 15 Nov 2022 11:05:47 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/14/22 14:06, Gerald Pfeifer wrote:
> 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.


I see it similarly and I'm trying to take the best out of it.

> 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?

For now, I'm not planning working on that in the future. Maybe, someone else
can carry on working on that.

> And would it make sense to convert at least our installation docs and
> for the GCC 13 release?

Yes, it's definitely doable as it's quite small, not split among too many .rst
files and the HTML version is mainly built at our server in order to populate

I'm willing to help anybody, but it won't be me who will suggest/send
the patches.

Thanks for understanding.

> Gerald

      reply	other threads:[~2022-11-15 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
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
2022-11-15 10:05     ` Martin Liška [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).