From: David Malcolm <dmalcolm@redhat.com>
To: "Gaius Mulley" <gaiusmod2@gmail.com>, "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2 16/19] modula2 front end: bootstrap and documentation tools
Date: Fri, 25 Nov 2022 12:10:36 -0500 [thread overview]
Message-ID: <5c7e9141f2974df4cae96eb43fac89d002b831a1.camel@redhat.com> (raw)
In-Reply-To: <875yf4h1by.fsf@debian>
On Thu, 2022-11-24 at 14:30 +0000, Gaius Mulley via Gcc-patches wrote:
> Martin Liška <mliska@suse.cz> writes:
>
> > On 11/8/22 14:22, Gaius Mulley wrote:
> > > Martin Liška <mliska@suse.cz> writes:
> > >
> > > should be good - I'll complete the rst output in the scripts,
> >
> > Hi.
> >
>
> Hi Martin,
>
> > As you probably noticed, the Sphinx migration didn't go well.
>
> Yes, sorry to see this didn't happen. Thank you for your hard work
> and
> I hope it can occur in the future.
Likewise, thanks for all your work on this.
>
> > However, it's still up to you if you want to use it or not for
> > Modula
> > 2.
>
> Once modula-2 is in master I'd like to revisit rst in devel/modula-2
> along with analyzer patches and m2 generics. If successful then
> submit
> patches in early stage 1.
Am I right in thinking the analyzer stuff would be an updated version
of the work you posted here:
https://gcc.gnu.org/pipermail/gcc-patches/2021-April/567953.html
?
Thanks
Dave
next prev parent reply other threads:[~2022-11-25 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 15:31 [PATCH] 16/19 " Gaius Mulley
2022-10-13 9:12 ` Martin Liška
2022-10-14 12:10 ` Gaius Mulley
2022-11-07 13:09 ` [PATCH v2 16/19] " Gaius Mulley
2022-11-07 13:47 ` Martin Liška
2022-11-08 13:22 ` Gaius Mulley
2022-11-24 11:53 ` Martin Liška
2022-11-24 14:30 ` Gaius Mulley
2022-11-25 16:25 ` Martin Liška
2022-11-25 17:10 ` David Malcolm [this message]
2022-11-27 16:51 ` Gaius Mulley
2022-10-20 12:42 ` [PATCH] 16/19 " Martin Liška
2022-10-28 13:05 ` Gaius Mulley
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=5c7e9141f2974df4cae96eb43fac89d002b831a1.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).