From: David Miller <davem@davemloft.net>
To: sven@narfation.org
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv8] net: Add batman-adv meshing protocol
Date: Thu, 16 Dec 2010 14:52:28 -0800 (PST) [thread overview]
Message-ID: <20101216.145228.27818669.davem@davemloft.net> (raw)
In-Reply-To: <201012162321.11580.sven@narfation.org>
From: Sven Eckelmann <sven@narfation.org>
Date: Thu, 16 Dec 2010 23:21:09 +0100
> This brings me to another topic. How do you want to get patches for batman-
> adv? Do you prefer to pull changes from a git tree or do you want do have them
> sent to netdev and you as real patches? Do you have special restrictions on
> the time were you want to except feature patches for the next kernel version
> (before Linus' merge window)?
Patches or GIT tree is fine. Either way it should be based upon
net-next-2.6
If you use a GIT tree, you should still post the individual patches
for review on netdev.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCHv8] net: Add batman-adv meshing protocol
Date: Thu, 16 Dec 2010 14:52:28 -0800 (PST) [thread overview]
Message-ID: <20101216.145228.27818669.davem@davemloft.net> (raw)
In-Reply-To: <201012162321.11580.sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
From: Sven Eckelmann <sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
Date: Thu, 16 Dec 2010 23:21:09 +0100
> This brings me to another topic. How do you want to get patches for batman-
> adv? Do you prefer to pull changes from a git tree or do you want do have them
> sent to netdev and you as real patches? Do you have special restrictions on
> the time were you want to except feature patches for the next kernel version
> (before Linus' merge window)?
Patches or GIT tree is fine. Either way it should be based upon
net-next-2.6
If you use a GIT tree, you should still post the individual patches
for review on netdev.
next prev parent reply other threads:[~2010-12-16 22:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 21:19 [B.A.T.M.A.N.] [PATCHv8] net: Add batman-adv meshing protocol Sven Eckelmann
2010-12-13 21:19 ` Sven Eckelmann
2010-12-16 22:01 ` [B.A.T.M.A.N.] " David Miller
2010-12-16 22:01 ` David Miller
2010-12-16 22:21 ` [B.A.T.M.A.N.] " Sven Eckelmann
2010-12-16 22:21 ` Sven Eckelmann
2010-12-16 22:52 ` David Miller [this message]
2010-12-16 22:52 ` David Miller
2010-12-16 22:21 ` [B.A.T.M.A.N.] " Greg KH
2010-12-16 22:21 ` Greg KH
2010-12-16 22:27 ` [B.A.T.M.A.N.] " David Miller
2010-12-16 22:27 ` David Miller
2010-12-16 22:28 ` [B.A.T.M.A.N.] [PATCH] Staging: batman-adv: Remove batman-adv from staging Sven Eckelmann
2010-12-16 22:28 ` Sven Eckelmann
2010-12-16 22:31 ` [B.A.T.M.A.N.] " David Miller
2010-12-16 22:31 ` David Miller
2010-12-16 23:23 ` [B.A.T.M.A.N.] " Greg KH
2010-12-16 23:23 ` Greg KH
2010-12-16 23:39 ` [B.A.T.M.A.N.] " Sven Eckelmann
2010-12-16 23:39 ` Sven Eckelmann
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=20101216.145228.27818669.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=netdev@vger.kernel.org \
--cc=sven@narfation.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.