linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
	linux-next@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: linux-next: pending wireless/wireless-current merge conflict 2008-07-02
Date: Wed, 2 Jul 2008 18:02:12 -0400	[thread overview]
Message-ID: <20080702220212.GA31582@tuxdriver.com> (raw)

I just sent a pull request for Dave that will result in a merge
conflict with in linux-next.  I have a sample merge available here:

	git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6 merge-test

Just a heads-up... :-)

John
-- 
John W. Linville
linville@tuxdriver.com

             reply	other threads:[~2008-07-02 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 22:02 John W. Linville [this message]
2008-07-08 20:30 ` linux-next: pending wireless/wireless-current merge conflict 2008-07-08 John W. Linville
2008-07-08 23:40   ` Stephen Rothwell
2008-07-08 23:44     ` David Miller
2008-07-08 23:47       ` Stephen Rothwell

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=20080702220212.GA31582@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=davem@davemloft.net \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).