From: "John W. Linville" <linville@tuxdriver.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Michael Buesch <mb@bu3sch.de>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.23-rc2-mm2
Date: Fri, 10 Aug 2007 17:43:40 -0400 [thread overview]
Message-ID: <20070810214340.GA28812@tuxdriver.com> (raw)
In-Reply-To: <20070810132019.bc218797.akpm@linux-foundation.org>
On Fri, Aug 10, 2007 at 01:20:19PM -0700, Andrew Morton wrote:
> git-wireless now has the usual git catastrophe when merging it against the
> recently-discovered net-2.6.24 tree, so I'll need to do something about
> that first.
I have rebased the wireless-dev tree, and the mm-master branch there
should specifically avoid these merge conflicts.
Hth!
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-08-10 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070809224254.11f42716.akpm@linux-foundation.org>
[not found] ` <20070810200801.GA16714@hall.aurel32.net>
2007-08-10 20:20 ` 2.6.23-rc2-mm2 Andrew Morton
2007-08-10 21:43 ` John W. Linville [this message]
2007-08-13 5:29 ` 2.6.23-rc2-mm2 (libertas) Randy Dunlap
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=20070810214340.GA28812@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=aurelien@aurel32.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.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;
as well as URLs for NNTP newsgroup(s).