public inbox for
 help / color / mirror / Atom feed
From: "Martin Liška" <>
To: Andrew Pinski <>, GCC Mailing List <>
Cc: GCC Patches <>,
	Gerald Pfeifer <>
Subject: Re: Revert Sphinx documentation [Was: Issues with Sphinx]
Date: Mon, 14 Nov 2022 09:38:28 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 11/14/22 03:49, Martin Liška wrote:
> I'm going to revert the patchset during today (Monday) and I'll send a patch with a couple
> of new changes that landed in the period of time we used Sphinx.

The revert is done and I included ce51e8439a491910348a1c5aea43b55f000ba8ac commit
that ports all the new documentation bits to Texinfo.

Web pages content will be updated with Jakub in the afternoon.


  reply	other threads:[~2022-11-14  8:38 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 [this message]
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

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