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: Greg KH <gregkh@suse.de>
Cc: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] Getting batman into staging
Date: Wed, 26 Aug 2009 20:25:48 +0200	[thread overview]
Message-ID: <20090826182548.GG16067@lunn.ch> (raw)
In-Reply-To: <20090825201457.GA5070@suse.de>

Hi Greg

CC: to the batman list should now work for you. Your email address has
been listed as O.K. to accept. There is an ongoing discussion about an
open list and fighting SPAM etc.

> But first off, what is keeping this code from being added to the "main"
> portion of the kernel tree?  Have you submitted it for inclusion there
> already?  If so, what was the response?  If not, why not?
 
I'm reasonably new to the project so don't know the history too
well. I get the impression the code has not been sent to lkml or
linux-net list. There seems to be a perception within the developers
that getting code into mainline is difficult, so why bother when it
has been going O.K. out of mainline. I think you saying it could go
into staging right now has taken quite a few people by surprise.

Is staging the right way to do this? Is posting to say linux-net
better for this sort of code?

> Sound good?  If so, send me some patches!

Assuming we do go via staging, do you want one jumbo patch, 6500 lines
of code, or should i break it up into smaller chunks?

   Thanks
        Andrew

       reply	other threads:[~2009-08-26 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090825200530.GA21951@lunn.ch>
     [not found] ` <20090825201457.GA5070@suse.de>
2009-08-26 18:25   ` Andrew Lunn [this message]
2009-08-26 21:11     ` [B.A.T.M.A.N.] Getting batman into staging Greg KH
2009-08-26  6:49 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=20090826182548.GG16067@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    --cc=gregkh@suse.de \
    /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