From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batman-adv: Refactor forward packet creation/destruction
Date: Tue, 24 May 2016 00:42:59 +0200 [thread overview]
Message-ID: <20160523224259.GC6623@otheros> (raw)
In-Reply-To: <1464041662-639-1-git-send-email-linus.luessing@c0d3.blue>
Looks like my git-send-email had a hiccup. Please ignore this
duplicate.
next prev parent reply other threads:[~2016-05-23 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 22:14 [B.A.T.M.A.N.] [PATCHv2] batman-adv: Refactor forward packet creation/destruction Linus Lüssing
2016-05-23 22:42 ` Linus Lüssing [this message]
2016-06-05 8:22 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2016-05-23 22:10 Linus Lüssing
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=20160523224259.GC6623@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.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.