From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Correct smaller typographical errors
Date: Sat, 2 Jan 2010 20:37:18 +0100 [thread overview]
Message-ID: <20100102193718.GM31328@lunn.ch> (raw)
In-Reply-To: <1262454706-6137-1-git-send-email-sven.eckelmann@gmx.de>
> There is also some sentence in the batman manpage which should maybe changed.
> Maybe a native english speaking person could check if it is valid and
> understandable.
>
> "B.A.T.M.A.N tries to find the best available connection by watching the
> uplinks throughput and the link quality."
It is O.K. I would probably say link, not uplink.
However, this basic description is not really correct, at least not
for batman-adv. The throughput is not used in deciding on links to
use. Maybe Marek should first review the document for technical
correctness and then i can look at the English.
Andrew
next prev parent reply other threads:[~2010-01-02 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 17:51 [B.A.T.M.A.N.] Correct smaller typographical errors Sven Eckelmann
2010-01-02 17:51 ` [B.A.T.M.A.N.] [PATCH 1/3] batctl: Correct typographical errors detected by lintian Sven Eckelmann
2010-01-02 17:51 ` [B.A.T.M.A.N.] [PATCH 2/3] batctl: Differentiate between hyphen and minus in manpage Sven Eckelmann
2010-01-02 17:51 ` [B.A.T.M.A.N.] [PATCH 3/3] batman: Correct typographical errors detected by lintian Sven Eckelmann
2010-01-02 19:37 ` Andrew Lunn [this message]
2010-01-04 0:14 ` [B.A.T.M.A.N.] Correct smaller typographical errors Marek Lindner
2010-01-04 6:20 ` [B.A.T.M.A.N.] Correct smaller typographical errorsy Andrew Lunn
2010-01-04 10:31 ` Marek Lindner
2010-01-04 10:51 ` [B.A.T.M.A.N.] Correct smaller typographical errors Andrew Lunn
2010-01-04 11:12 ` Marek Lindner
2010-01-04 19:11 ` Andrew Lunn
2010-01-07 4:59 ` Marek Lindner
2010-01-07 6:15 ` Andrew Lunn
2010-01-07 13:33 ` 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=20100102193718.GM31328@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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