From: Adrian Bunk <bunk@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: khc@pm.waw.pl, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Please pull - generic HDLC
Date: Mon, 13 Oct 2008 08:53:56 +0300 [thread overview]
Message-ID: <20081013055356.GA29938@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20081012.144704.39192150.davem@davemloft.net>
On Sun, Oct 12, 2008 at 02:47:04PM -0700, David Miller wrote:
> From: Krzysztof Halasa <khc@pm.waw.pl>
> Date: Sun, 12 Oct 2008 23:12:16 +0200
>
> > David,
> >
> > The following changes since commit
> > f3073ac76755abd63b1d4c3d145f4c15b65b5355 (i.e., your netdev-2.6):
> > Guennadi Liakhovetski (1): smc911x: Fix external PHY detection
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux-2.6.git for-david
>
> You've missed the networking merge window, as I stated the other
> day I'm not taking any more networking changes.
>
> You should have merged this in earlier.
>...
Ignoring whether it will go into 2.6.28 or 2.6.29 there seems to be a
more fundamental issue:
The over 3 weeks old -next already contains mostly the same as the HDLC
tree contains now.
The thing you two should sort out is why the tree ended up as an own
tree in -next instead of pull requests to David long ago.
E.g. the netdev and wireless trees also don't go into -next, but instead
with frequent pull requests to David.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-10-13 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 21:12 Please pull - generic HDLC Krzysztof Halasa
2008-10-12 21:47 ` David Miller
2008-10-12 22:35 ` Krzysztof Halasa
2008-10-13 5:53 ` Adrian Bunk [this message]
2008-10-13 14:53 ` Krzysztof Halasa
2008-10-13 18:23 ` David Miller
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=20081013055356.GA29938@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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