From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] doc: add intro stolen from the wiki
Date: Tue, 16 Jun 2020 02:38:26 +0100 [thread overview]
Message-ID: <1d164023-8e9d-8950-7fec-b1bd7b673c31@ramsayjones.plus.com> (raw)
In-Reply-To: <20200616001122.65350-1-luc.vanoostenryck@gmail.com>
On 16/06/2020 01:11, Luc Van Oostenryck wrote:
> The wiki has a small into, perfectable but nice
s/into/intro/ or s/into/introduction/
s/perfectable but/which could be improved, but is/
> enough while the doc here has no such thing.
s/enough/enough,/
>
> So, copy the intro from the wiki into the entrypoint
s/intro/introduction/ maybe.
ATB,
Ramsay Jones
> of the documentation (and convert the wikimedia markup
> into restructuredtext).
>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> ---
> Documentation/index.rst | 37 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/Documentation/index.rst b/Documentation/index.rst
> index eb3de63c9ca7..415da4bb27af 100644
> --- a/Documentation/index.rst
> +++ b/Documentation/index.rst
> @@ -6,6 +6,43 @@ Welcome to sparse's documentation
> .. toctree::
> :maxdepth: 1
>
> +About Sparse
> +------------
> +
> +Sparse, the semantic parser, provides a compiler frontend capable of
> +parsing most of ANSI C as well as many GCC extensions, and a collection
> +of sample compiler backends, including a static analyzer also called `sparse`.
> +Sparse provides a set of annotations designed to convey semantic information
> +about types, such as what address space pointers point to, or what locks
> +function acquires or releases.
> +
> +Linus Torvalds started writing Sparse in 2003, initially targeting issues such
> +as mixing pointers to user address space and pointers to kernel address space.
> +
> +Josh Triplett was Sparse's first maintainer in 2006. This role was taken over
> +by Christopher Li in 2009 and by Luc Van Oostenryck in late 2018.
> +
> +Getting Sparse
> +--------------
> +
> +You can find released versions of sparse at http://www.kernel.org/pub/software/devel/sparse/dist/
> +
> +Obtaining sparse via Git
> +~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +Sparse uses the `Git version control system <http://git-scm.com/>`_. You can obtain the most recent version of sparse directly from the Git repository with the command::
> +
> + git clone git://git.kernel.org/pub/scm/devel/sparse/sparse.git
> +
> +You can also `browse the Git repository <https://git.kernel.org/pub/scm/devel/sparse/sparse.git>`_.
> +
> +Mailing list
> +~~~~~~~~~~~~
> +
> +Discussions about sparse occurs on the sparse mailing list, linux-sparse@vger.kernel.org. To subscribe to the list, send an email with ``subscribe linux-sparse`` in the body to ``majordomo@vger.kernel.org``.
> +
> +You can browse the list archives at https://marc.info/?l=linux-sparse.
> +
> User documentation
> ------------------
> .. toctree::
>
next prev parent reply other threads:[~2020-06-16 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 0:11 [PATCH] doc: add intro stolen from the wiki Luc Van Oostenryck
2020-06-16 1:38 ` Ramsay Jones [this message]
2020-06-16 20:57 ` 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=1d164023-8e9d-8950-7fec-b1bd7b673c31@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;
as well as URLs for NNTP newsgroup(s).