From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/olsr
Date: Wed, 27 Aug 2008 13:18:54 -0700 (PDT) [thread overview]
Message-ID: <20080827201854.D36B23C84E@busybox.net> (raw)
Author: jacmet
Date: 2008-08-27 13:18:54 -0700 (Wed, 27 Aug 2008)
New Revision: 23252
Log:
olsr: fix long help text lines
Modified:
trunk/buildroot/package/olsr/Config.in
Changeset:
Modified: trunk/buildroot/package/olsr/Config.in
===================================================================
--- trunk/buildroot/package/olsr/Config.in 2008-08-27 20:18:51 UTC (rev 23251)
+++ trunk/buildroot/package/olsr/Config.in 2008-08-27 20:18:54 UTC (rev 23252)
@@ -1,11 +1,11 @@
config BR2_PACKAGE_OLSR
bool "OLSR mesh networking Daemon"
help
- olsr
-
- The Optimized Link State Routing protocol (OLSR) is a routing protocol that is optimised
- for mobile ad-hoc networks, sometimes called wireless mesh networks. It is a proactive
- link-state routing protocol that floods a full topology table to all nodes in the network
- which then compute optimal forwarding paths locally.
+ The Optimized Link State Routing protocol (OLSR) is a
+ routing protocol that is optimised for mobile ad-hoc
+ networks, sometimes called wireless mesh networks. It is a
+ proactive link-state routing protocol that floods a full
+ topology table to all nodes in the network which then
+ compute optimal forwarding paths locally.
http://www.olsr.org/
next reply other threads:[~2008-08-27 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:18 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-10 0:27 [Buildroot] svn commit: trunk/buildroot/package/olsr ulf at uclibc.org
2007-12-11 19:53 vanokuten at uclibc.org
2007-10-18 22:40 vanokuten at uclibc.org
2007-09-19 21:31 aldot at uclibc.org
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=20080827201854.D36B23C84E@busybox.net \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.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