From: Germano Massullo <germano.massullo@gmail.com>
To: Sven Eckelmann <sven@narfation.org>, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Creating alfred code documentation
Date: Mon, 14 Mar 2016 22:50:09 +0100 [thread overview]
Message-ID: <56E73211.5070808@gmail.com> (raw)
In-Reply-To: <1817507.YIectHPgqy@sven-edge>
[-- Attachment #1.1: Type: text/plain, Size: 531 bytes --]
Il 12/03/2016 18:55, Sven Eckelmann ha scritto:
> I am currently not sure about the "explaining also most important
> local variables"
For example in the function
=========
static int vis_read_answer(struct globals *globals)
{
const struct vis_print_ops *ops;
struct vis_v1 *vis_data;
uint16_t len;
struct vis_iface *ifaces;
struct vis_entry *vis_entries;
// CUT
=========
I would stress the purposes description of
struct vis_v1 *vis_data
struct vis_iface *ifaces
struct vis_entry *vis_entries
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-14 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 16:12 [B.A.T.M.A.N.] Creating alfred code documentation Germano Massullo
2016-03-12 17:55 ` Sven Eckelmann
2016-03-14 21:50 ` Germano Massullo [this message]
2016-09-30 5:38 ` Germano Massullo
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=56E73211.5070808@gmail.com \
--to=germano.massullo@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.org \
/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