From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.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.] A.L.F.R.E.D.+vis manpages missing
Date: Sun, 28 Jul 2013 21:44:14 +0200 [thread overview]
Message-ID: <20130728194413.GA3746@pandem0nium> (raw)
In-Reply-To: <CAKEO+ThRiXtRyek2AJBbfkgwzJODSDn7mOSiVLLRfww=kfE_tQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Hey Braden,
thanks for your feedback!
On Sun, Jul 28, 2013 at 09:02:36PM +0200, Braden Aran wrote:
> Hi,
>
> it seems the A.L.F.R.E.D. component and his vis is getting released
> soon http://git.open-mesh.org/alfred.git/commit/fac591b6d8a8a9eaca33a0d7614433cbca23f55f
Actually, alfred was just release a couple of hours ago, although the
announcement is to come soon after.
>
> But where are the man pages? Don't you think it would be nice for
> people when they can read how it is used in a standard unix way? At
> least they need to use it because this functionality is removed in
> batman-adv soon.
> http://www.open-mesh.org/projects/open-mesh/wiki/2013-07-29-batman-adv-2013-3-0-release?version=1
There is quite a lot of information in the README to get going, but yes,
a manpage would be great. If there is anyone who could contribute one,
I would be very happy, if not I'll write one myself prior to the next
release.
> I can't find the manpages for both binaries in the tarball
> http://downloads.open-mesh.org/batman/stable/sources/alfred/alfred-2013.3.0.tar.gz
There won't be one for now. Please stick to the README for now.
> And isn't the name vis potentially problematic and bad named after
> all? "vis" doesn't tell anyone about the connection to batman-adv and
> it sounds more like a GUI program to visualize stuff (mathematical
> equations?). And it clashes directly with the vis of batmand. So I
> cannot install both on the same system in a unix manner.
I don't know if it sounds like a GUI program, we have used that name
for years in the various iterations and no complaints so far. The
clash with the old batmand-vis is true however. I'm not sure if anyone
still uses that, but I'm open to suggestions how to handle that.
Is there anyone using the old vis? I'd appreciate any ideas, discussions,
comments. :)
Cheers,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-07-28 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 19:02 [B.A.T.M.A.N.] A.L.F.R.E.D.+vis manpages missing Braden Aran
2013-07-28 19:44 ` Simon Wunderlich [this message]
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=20130728194413.GA3746@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.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