netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: Please pull 'upstream' branch of wireless-2.6.git
Date: Mon, 25 Sep 2006 20:09:37 -0400	[thread overview]
Message-ID: <45186FC1.8000005@garzik.org> (raw)
In-Reply-To: <20060925215037.GG16949@tuxdriver.com>

pulled


  parent reply	other threads:[~2006-09-26  0:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 21:50 Please pull 'upstream' branch of wireless-2.6.git John W. Linville
2006-09-25 21:55 ` wireless-2.6 now has a 'pending' branch (was Re: Please pull 'upstream' branch of wireless-2.6.git) John W. Linville
2006-09-26  0:09 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-01  3:47 Please pull 'upstream-fixes' branch of wireless-2.6.git John W. Linville
2006-11-01  3:48 ` Please pull 'upstream' " John W. Linville
2006-11-06  8:02   ` Jeff Garzik

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=45186FC1.8000005@garzik.org \
    --to=jeff@garzik.org \
    --cc=linville@tuxdriver.com \
    --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;
as well as URLs for NNTP newsgroup(s).