Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [ANNOUNCE] Sparse v0.6.2-rc1
Date: Sun, 14 Jun 2020 23:54:45 +0200	[thread overview]
Message-ID: <20200614215445.rtfbx23ve57fhlbr@ltop.local> (raw)
In-Reply-To: <c80024d2-6d91-4fe7-a919-3edcf4a9b80a@ramsayjones.plus.com>

On Sun, Jun 14, 2020 at 08:35:51PM +0100, Ramsay Jones wrote:
> 
> 
> On 13/06/2020 03:07, Luc Van Oostenryck wrote:
> > Sparse v0.6.2-rc1 is now out.
> 
> Tested in the usual places (Linux Mint 19.3, 64-bit and 32-bit and
> 64-bit cygwin) and in the usual way; no issues found!

Thanks a lot. Here I tested it on 64-bit Debian (latest + unstable)
and Ubuntu, and also on ARM64, ARM(32), ppc64, sparc64, mips64.
I'll give a try later to some BSD.

> Well, I say no issues - I did notice some spelling errors and
> the formatting of the release notes does not look correct to
> me (https://sparse.docs.kernel.org/en/latest/release-notes/v0.6.2.html).
> Unfortunately, I don't know anything about the documentation tools
> you are using, so I can't try to fix this. (It seems to be the only
> attempt at nested 'bulleted lists', ...)

Yes, I saw that too now. I thought I had fixed it but visibly it
wasn't. It should be really fixed now.

[(Just FYI) The format of the doc is either reStructuredText
(.rst) or MarkDown (.md). Both are much less simple than they
appear to be but they have the huge advantage to almost look
as if there is no markup at all/as if written 'naturally' in
ASCII. Much much more readable than man-pages or html markup.

The system used to generate the resulting HTML is Sphinx.
It has the huge advantage to be very easy to install/to have
near-zero dependencies: it's just a single python package.
To use it, it's enough to just 'cd Documentation; make html'
and the result can be found in 'build/html'. But I confess,
most of the time, I'm too lazy to do that, I just push it
on github which trigger a build on readthedocs.io (which
then nicely send me an email if there is an error).]

-- Luc

  reply	other threads:[~2020-06-14 21: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 [this message]
2020-06-14 23:37     ` Ramsay Jones
2020-06-15 16:38       ` Luc Van Oostenryck
2020-06-15 22:54         ` Ramsay Jones
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=20200614215445.rtfbx23ve57fhlbr@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.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