From: "Martin Liška" <mliska@suse.cz>
To: Philip Herron <philip.herron@embecosm.com>
Cc: "Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Gcc Patch List" <gcc-patches@gcc.gnu.org>,
"Manuel López-Ibáñez" <manu@gcc.gnu.org>
Subject: Re: Rust frontend patches v1
Date: Wed, 24 Aug 2022 16:02:25 +0200 [thread overview]
Message-ID: <6b3ae18e-2e8d-6795-1056-8ee9fae3741d@suse.cz> (raw)
In-Reply-To: <CAB2u+n2pjVtbr-XjP9qHbOHX46ocmOiwx5K0Eft8ZKjRqtuRqA@mail.gmail.com>
On 8/24/22 15:51, Philip Herron wrote:
> Hi Martin,
>
> Not right now, it is on the to-do list, but do we have to do it in texinfo?
Well, I still hope we will move to Sphinx (and remove Texinfo) after the Cauldron.
Anyway, using Sphinx is even now possible as a default documentation formal (see libgccjit,
Ada manuals), where one exports Sphinx to texinfo.
Cheers,
Martin
>
> Thanks
>
> --Phil
>
> On Wed, 24 Aug 2022 at 14:49, Martin Liška <mliska@suse.cz> wrote:
>>
>> On 8/15/22 16:33, Martin Liška wrote:
>>> On 8/15/22 16:07, Manuel López-Ibáñez via Gcc-patches wrote:
>>>> Dear Philip,
>>>>
>>>> Another thing to pay attention to is the move to Sphinx for documentation:
>>>> https://gcc.gnu.org/pipermail/gcc/2022-August/239233.html
>>>
>>> Hi.
>>>
>>> Which is something I can help you with. I have a script that converts a texinfo documentation
>>> to Sphinx.
>>
>> @Herron: Do you have any significant documentation changes in the rust branch right now?
>> I can't see any.
>>
>> Thanks,
>> Martin
>>
>>>
>>> Cheers,
>>> Martin
>>
prev parent reply other threads:[~2022-08-24 14:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 13:40 herron.philip
2022-07-27 13:40 ` [PATCH Rust front-end v1 1/4] Add skeleton Rust front-end folder herron.philip
2022-07-27 13:40 ` [PATCH Rust front-end v1 2/4] Add Rust lang TargetHooks for i386 and x86_64 herron.philip
2022-07-28 9:57 ` Jakub Jelinek
2022-07-28 10:38 ` Thomas Schwinge
2022-07-28 10:51 ` Philip Herron
2022-07-28 11:08 ` Thomas Schwinge
2022-07-28 11:41 ` Philip Herron
2022-07-27 13:40 ` [PATCH Rust front-end v1 3/4] Add Rust target hooks to ARM herron.philip
2022-07-27 14:13 ` Richard Earnshaw
2022-07-27 16:45 ` Rust frontend patches v1 David Malcolm
2022-07-28 9:39 ` Philip Herron
2022-08-10 18:56 ` Philip Herron
2022-08-10 19:06 ` David Malcolm
2022-08-12 20:45 ` Mike Stump
2022-08-15 14:07 ` Manuel López-Ibáñez
2022-08-15 14:33 ` Martin Liška
2022-08-24 13:48 ` Martin Liška
2022-08-24 13:51 ` Philip Herron
2022-08-24 14:02 ` 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:
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=6b3ae18e-2e8d-6795-1056-8ee9fae3741d@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=lopezibanez@gmail.com \
--cc=manu@gcc.gnu.org \
--cc=philip.herron@embecosm.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).