From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-03-04
Date: Tue, 4 Mar 2008 17:16:41 -0500 [thread overview]
Message-ID: <20080304221641.GC3158@tuxdriver.com> (raw)
In-Reply-To: <20080304.134003.223058560.davem@davemloft.net>
On Tue, Mar 04, 2008 at 01:40:03PM -0800, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Tue, 4 Mar 2008 16:29:53 -0500
>
> > Here is today's round of fixes for the 2.6.25 tree. These are mostly
> > simple fixes, even one-liners. The rc80211-pid patch is, of course, an
> > exception...
>
> Please don't just clone Linus's tree, pull net-2.6, and then stuff
> things on top of that and ask me to pull. I end up being forced to
> end up with a merge of Linus's current tree as a result, and that's
> not how this is supposed to work.
>
> I keep net-2.6 stable for a reason. Jeff did what you're doing right
> now the other week and now you're doing it too.
Sorry, Dave. I'll fix it up and post a new request.
John
--
John W. Linville
linville@tuxdriver.com
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-2.6 2008-03-04
Date: Tue, 4 Mar 2008 17:16:41 -0500 [thread overview]
Message-ID: <20080304221641.GC3158@tuxdriver.com> (raw)
In-Reply-To: <20080304.134003.223058560.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On Tue, Mar 04, 2008 at 01:40:03PM -0800, David Miller wrote:
> From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
> Date: Tue, 4 Mar 2008 16:29:53 -0500
>
> > Here is today's round of fixes for the 2.6.25 tree. These are mostly
> > simple fixes, even one-liners. The rc80211-pid patch is, of course, an
> > exception...
>
> Please don't just clone Linus's tree, pull net-2.6, and then stuff
> things on top of that and ask me to pull. I end up being forced to
> end up with a merge of Linus's current tree as a result, and that's
> not how this is supposed to work.
>
> I keep net-2.6 stable for a reason. Jeff did what you're doing right
> now the other week and now you're doing it too.
Sorry, Dave. I'll fix it up and post a new request.
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-04 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 21:29 pull request: wireless-2.6 2008-03-04 John W. Linville
2008-03-04 21:40 ` David Miller
2008-03-04 21:40 ` David Miller
2008-03-04 22:16 ` John W. Linville [this message]
2008-03-04 22:16 ` John W. Linville
2008-03-04 22:38 ` David Miller
2008-03-04 22:38 ` David Miller
2008-03-05 0:23 ` pull request (2nd try): " John W. Linville
2008-03-05 1:02 ` 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=20080304221641.GC3158@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@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 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.