From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [ANNOUNCE] Sparse v0.6.2-rc1
Date: Mon, 15 Jun 2020 23:54:46 +0100 [thread overview]
Message-ID: <9fecbef9-12c8-6374-d5cd-914c3b009afa@ramsayjones.plus.com> (raw)
In-Reply-To: <CAExDi1RbuRvkQb0DAYZUdwj+XQvVn91D8rU_-_bkybfCqi10eg@mail.gmail.com>
On 15/06/2020 17:38, Luc Van Oostenryck wrote:
> On Mon, Jun 15, 2020 at 12:37:28AM +0100, Ramsay Jones wrote:
>> I just installed python-sphinx (on LM 19.3 it is the python2
>> version) to give it a try, and it failed:
>>
>> $ make html
>> Running Sphinx v1.6.7
>
> This is probably too old (running 3.0 here but IIRC 2.7 or
> 2.8 should be OK).
I'm not that surprised! I will wait until LM20 which, being based
on Ubuntu 20.04, should hopefully have a sufficiently new version.
BTW, the on-line version of the v0.6.2 release notes look good to
me now ... except one thing! ;-)
This part of the release notes:
* fully propagate declarations downward.
For example, it means that code like:
static int foo(void);
int foo(void) { return 0; }
now behaves as expected: foo() is effectively static.
... has the two lines of code formatted as a 'filled paragraph'.
I assume that some 'code-block' marker(s) of some description are
required to format this correctly.
ATB,
Ramsay Jones
next prev parent reply other threads:[~2020-06-15 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 2:07 [ANNOUNCE] Sparse v0.6.2-rc1 Luc Van Oostenryck
2020-06-14 19:35 ` Ramsay Jones
2020-06-14 21:54 ` Luc Van Oostenryck
2020-06-14 23:37 ` Ramsay Jones
2020-06-15 16:38 ` Luc Van Oostenryck
2020-06-15 22:54 ` Ramsay Jones [this message]
2020-06-15 23:33 ` Luc Van Oostenryck
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=9fecbef9-12c8-6374-d5cd-914c3b009afa@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@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