All of lore.kernel.org
 help / color / mirror / Atom feed
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-next-2.6 2008-06-09
Date: Tue, 10 Jun 2008 08:17:49 -0400	[thread overview]
Message-ID: <20080610121749.GA1571@tuxdriver.com> (raw)
In-Reply-To: <20080610.021937.252613352.davem@davemloft.net>

On Tue, Jun 10, 2008 at 02:19:37AM -0700, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Mon, 9 Jun 2008 17:07:37 -0400
> 
> > Tons of new stuff intended for 2.6.27.  Please let me know if there are
> > problems!
>  ...
> > The following changes since commit 5b06c85c3b96fa8db632f1ee94f99a2bd0215f3a:
> >   Allan Stephens (1):
> >         tipc: Cosmetic cleanup of topology service code
> > 
> > are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git
> 
> Surely you meant to specify the "master" branch in that URL?
> 
> I assumed that, pulled, resolved the conflicts, and pushed
> back out to net-next-2.6

Yes, thanks!

-- 
John W. Linville
linville@tuxdriver.com

      reply	other threads:[~2008-06-10 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 12:40 pull request: wireless-next-2.6 2008-05-22 John W. Linville
2008-05-22 12:40 ` John W. Linville
2008-06-03 18:53 ` John W. Linville
2008-06-03 18:53   ` John W. Linville
2008-06-03 19:49   ` pull request: wireless-next-2.6 2008-06-03 John W. Linville
2008-06-03 19:49     ` John W. Linville
2008-06-09 20:42     ` John W. Linville
2008-06-09 20:42       ` John W. Linville
2008-06-09 21:07       ` pull request: wireless-next-2.6 2008-06-09 John W. Linville
2008-06-09 21:07         ` John W. Linville
2008-06-10  9:19         ` David Miller
2008-06-10 12:17           ` John W. Linville [this message]

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=20080610121749.GA1571@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.