From: derek@knosof.co.uk (Derek M Jones)
To: cocci@systeme.lip6.fr
Subject: [Cocci] version 1.0.0
Date: Mon, 20 Apr 2015 14:43:28 +0100 [thread overview]
Message-ID: <55350280.8040109@knosof.co.uk> (raw)
In-Reply-To: <20150420091540.GA7998@pema>
S?bastien,
> However, improving the user documentation is part of what I am supposdd to
> do on Coccinelle dugring this year. That's why, I'd be interested
> in any feedback. In particular, if you could let me know which are
> the areas which, according to you, are not so well documented, that
> woudl be helpful.
More and more people are hosting their documentation on github,
written using markdown.
https://help.github.com/articles/github-flavored-markdown/
Some examples:
https://github.com/showcases/writing
This approach also makes it easier for you to allow others to
contribute.
--
Derek M. Jones Software analysis
tel: +44 (0)1252 520667 blog:shape-of-code.coding-guidelines.com
next prev parent reply other threads:[~2015-04-20 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 15:37 [Cocci] version 1.0.0 Julia Lawall
2015-04-19 17:01 ` Derek M Jones
2015-04-19 17:14 ` Julia Lawall
2015-04-20 8:10 ` Wolfram Sang
2015-04-20 8:19 ` Julia Lawall
2015-04-20 8:25 ` SF Markus Elfring
2015-04-20 9:15 ` Sébastien Hinderer
2015-04-20 13:21 ` [Cocci] documentation improvements SF Markus Elfring
2015-04-20 13:43 ` Derek M Jones [this message]
2015-04-23 18:56 ` [Cocci] version 1.0.0 SF Markus Elfring
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=55350280.8040109@knosof.co.uk \
--to=derek@knosof.co.uk \
--cc=cocci@systeme.lip6.fr \
/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