All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Huldt <christian@solvare.se>
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.] collaboration-group on batman-adv installation & application
Date: Thu, 19 Apr 2012 20:46:57 +0200	[thread overview]
Message-ID: <67286569-54F7-4AF1-A6E8-E710516F9155@solvare.se> (raw)
In-Reply-To: <CAJuY50yHZUZ6USgMYHEnZHc+hzb0nu+UJ4wRz2sCSEF+f=pybA@mail.gmail.com>

19 apr 2012 kl. 18:39 skrev 3zl Trizonelabs:

> I would like to organize a kind of collaboration-site on all practical
> aspects of batman-adv installation.
> 
> It could be a platform to discuss, interchange know how dealing with
> all aspects of batman-adv mesh application
> 
> As i did switch from AWDS-L2 to batman-adv, i am about to start
> gathering some samples of code & information i thought would be viable
> to help getting a batman-mesh running.
> 
> Anyone interested please respond to discuss how this might be setup.
> (example: www.teamlab.com )

+1

I think one of the most important things would be an allowing athmosphere, 
as a former lecturer I think that the "stupid questions" are the most fundamental ones

  reply	other threads:[~2012-04-19 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 16:39 [B.A.T.M.A.N.] collaboration-group on batman-adv installation & application 3zl Trizonelabs
2012-04-19 18:46 ` Christian Huldt [this message]
2012-04-28  7:09   ` Guido Iribarren
2012-04-28 10:19     ` 3zl Trizonelabs
2012-04-28 11:40     ` [B.A.T.M.A.N.] [Interop-dev] " Mitar
2012-04-28 12:53       ` 3zl Trizonelabs
2012-04-28 14:59       ` Guido Iribarren
2012-04-28 20:57         ` 3zl Trizonelabs
2012-05-07 19:05           ` Guido Iribarren

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=67286569-54F7-4AF1-A6E8-E710516F9155@solvare.se \
    --to=christian@solvare.se \
    --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.