All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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: Tue, 29 Sep 2009 17:19:37 +0800	[thread overview]
Message-ID: <200909291719.37794.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20090929052511.GZ16067@lunn.ch>

On Tuesday 29 September 2009 13:25:11 Andrew Lunn wrote:
> > This is the best alternative that I have found.  They charge $4/month
> > for up to 1000 subscribers and 1-8 posts/day.
> 
> I would read the small print. We currently have 100 messages/month to
> a closed list. Once it is an open list, and well publicised, the
> amount of spam will increase dramatically. I personally get 100-200
> spams per day. Does this 1-8 posts per day include or exclude spam?

Ok, if this list is not going to make it I only see 2 options (feel free to 
add more):

* We drop the requirement to keep the domain name for the list and migrate 
everyone to the new list.
* We create the additional new list while keeping the old one. The new list is 
for the communication with the kernel developers.

Opinions ?

Regards,
Marek


PS: Big thanks to Jacob for digging into this.

  reply	other threads:[~2009-09-29  9:19 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
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 [this message]
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=200909291719.37794.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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 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.