From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: rename bridge loop avoidance claim types
Date: Mon, 25 Jun 2012 16:30:01 +0200 [thread overview]
Message-ID: <201206251630.01504.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1340447658-27405-2-git-send-email-siwu@hrz.tu-chemnitz.de>
On Saturday, June 23, 2012 12:34:18 Simon Wunderlich wrote:
> for consistency reasons within the code and with the documentation,
> we should always call it "claim" and "unclaim".
>
> Signed-off-by: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
> ---
> bridge_loop_avoidance.c | 18 +++++++++---------
> packet.h | 4 ++--
> 2 files changed, 11 insertions(+), 11 deletions(-)
Applied in revision f9bb019.
Thanks,
Marek
next prev parent reply other threads:[~2012-06-25 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 10:34 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: correct comments in bridge loop avoidance Simon Wunderlich
2012-06-23 10:34 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: rename bridge loop avoidance claim types Simon Wunderlich
2012-06-25 14:30 ` Marek Lindner [this message]
2012-06-25 14:28 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: correct comments in bridge loop avoidance Marek Lindner
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=201206251630.01504.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox