From: Philipp Psurek <philipp.psurek@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.] Need some help to understand the code
Date: Sat, 02 Apr 2016 09:57:49 +0200 [thread overview]
Message-ID: <1459583869.10379.7.camel@gmail.com> (raw)
In-Reply-To: <2105035.hUCDNLol8h@sven-edge>
Thank you very much Sven,
I already tried [3] and yes, the API has changed ;-) Some of the
examples has been ported ... I hope to understand this soon.
Am Samstag, den 02.04.2016, 08:15 +0200 schrieb Sven Eckelmann:
> On Friday 01 April 2016 14:27:31 Philipp Psurek wrote:
> [...]
[...]
>
> I don't know what tasks are currently open in the Freifunk GSoC. But
> if it is multicast related then you may better ask Linus about some
> more literature.
OK
[...]
> [3] http://www.oreilly.com/openbook/linuxdrive3/book/
thanx again and
best regards,
Philipp
next prev parent reply other threads:[~2016-04-02 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 12:27 [B.A.T.M.A.N.] Need some help to understand the code Philipp Psurek
2016-04-02 6:15 ` Sven Eckelmann
2016-04-02 7:57 ` Philipp Psurek [this message]
2016-04-04 23:15 ` Linus Lüssing
2016-04-05 7:11 ` Sven Eckelmann
2016-04-05 7:36 ` Hans-Werner Hilse
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=1459583869.10379.7.camel@gmail.com \
--to=philipp.psurek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.