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: postmaster@vger.kernel.org
Cc: b.a.t.m.a.n@lists.open-mesh.net
Subject: [B.A.T.M.A.N.] VGER mailing list request
Date: Sun, 4 Oct 2009 19:41:27 +0200	[thread overview]
Message-ID: <20091004174127.GB3685@lunn.ch> (raw)

> I'm sure your project is very interesting, but it falls short of the
> scope for having the list crated on vger.
> 
> Generally, we host lists for kernel projects and their tools for which
> they are already upstream or for which their upstream acceptance is
> imminent.
> 
> I've never seen the BATMAN kernel bits even submitted for review on
> netdev@vger.kernel.org and getting your code upstream via submission
> there would be a prerequesite before we could be discussing a mailing
> list on vger.
> 
> I'm not even sure the getting your kernel bits upstream is even
> something you want, or whether the networking maintainer (that's
> me :-) would consider your code and approach acceptable.

Hi David

Let me fill in some of the background.

We have been talking to GregKH about submitting the code to staging.
Greg has said he is happy to accept the patches for staging, since the
code is totally self contained, mostly passed checkpatch apart from
some long lines, sparse clean etc. And we have a TODO list of things
we think need fixing before it can leave staging.

However, at the moment we are using a closed list. Your reply to this
email is going to bounce from the list server. Before we submit to
staging and hopefully start getting feedback from kernel experts, we
would like to move to an open list. The current list server does not
have good enough Spam filtering for an open list. So we are looking
for a list server provider who we could use. vger seemed like an
obvious choice.

Is likely acceptance in staging sufficient for "...for which their
upstream acceptance is imminent."?

   Thanks
          Andrew

             reply	other threads:[~2009-10-04 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 17:41 Andrew Lunn [this message]
     [not found] ` <20091004.171221.67525397.davem@davemloft.net>
2009-10-05  6:34   ` [B.A.T.M.A.N.] VGER mailing list request Andrew Lunn
2009-10-05 11:48     ` [B.A.T.M.A.N.] OT: M$FT (was Re: VGER mailing list request) Bernd Petrovitsch
  -- strict thread matches above, loose matches on Subject: below --
2009-10-04  3:15 [B.A.T.M.A.N.] VGER mailing list request Jacob Marble
2009-10-04  7:38 ` Andrew Lunn
2009-10-04 17:23 ` Andrew Lunn

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=20091004174127.GB3685@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    --cc=postmaster@vger.kernel.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