public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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.] mailing list migration (was: development flow)
Date: Mon, 28 Sep 2009 07:03:22 +0200	[thread overview]
Message-ID: <20090928050322.GW16067@lunn.ch> (raw)
In-Reply-To: <5161afcd0909272029t2f3054f2t39e99aa28fe3a453@mail.gmail.com>

> Sorry for the delay, busy week.  So, I'm looking for a mailing host that:
> 
> a) has experience hosting, and so can filter spam without hassle
> b) lets us use open-mesh.net instead of super-duper-mailing-host.com
> c) hosts open source gratis

a and b are must have, c would be nice. 
 
> I've looked at sourceforge, but their mailing list service looks very
> canned and they only allow <listname>@lists.sourceforge.net.  Also, SF
> already has a project called batman, so I created one called batman2
> (there are surely more creative project names available).  I have
> created a test account:
> https://lists.sourceforge.net/lists/admin/batman2-test

There was briefly a discussion about renaming batman-adv to something
else, but that discussion seemed to of died before reaching any
conclusion. So for the moment i would suggest for the moment we keep
with batman.

        Andrew

  parent reply	other threads:[~2009-09-28  5:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30  1:36 [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Linus Lüssing
2009-08-30  1:59 ` Linus Lüssing
2009-08-30  7:37 ` Andrew Lunn
2009-08-30 20:23   ` Simon Wunderlich
2009-08-31  5:26     ` [B.A.T.M.A.N.] development flow Marek Lindner
2009-08-31  5:50       ` Andrew Lunn
2009-09-01 18:47         ` Marek Lindner
2009-09-02  6:18           ` Andrew Lunn
2009-09-03  6:06             ` Marek Lindner
2009-09-08 16:01               ` Andrew Lunn
2009-09-08 17:54                 ` [B.A.T.M.A.N.] mailing list migration (was: development flow) Marek Lindner
2009-09-18 21:14                   ` Jacob Marble
2009-09-18 21:19                     ` Jacob Marble
2009-09-19  7:59                       ` Andrew Lunn
2009-09-28  3:29                         ` Jacob Marble
2009-09-28  3:31                           ` Jacob Marble
2009-09-28  5:03                           ` Andrew Lunn [this message]
2009-09-28  6:12                             ` Jacob Marble
2009-09-29  5:06                               ` Jacob Marble
2009-09-29  5:25                                 ` Andrew Lunn
2009-09-29  9:19                                   ` Marek Lindner
2009-09-29 15:56                                     ` Jacob Marble
2009-09-29 16:14                                       ` Sven Eckelmann
2009-09-30  5:39                                         ` Jacob Marble
2009-09-30 19:27                                           ` Marek Lindner
2009-09-29 15:38                                   ` Jacob Marble
2009-08-30 19:55 ` [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Simon Wunderlich
2009-08-30 20:15   ` Andrew Lunn
2009-08-30 21:47   ` Linus Lüssing
2009-08-31  5:28     ` Andrew Lunn
2009-09-01 20:47   ` Linus Lüssing
2009-09-04 18:58     ` Linus Lüssing

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=20090928050322.GW16067@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