linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: New list for wireless dev discussions
Date: Fri, 09 Feb 2007 15:00:58 -0600	[thread overview]
Message-ID: <45CCE10A.3050109@lwfinger.net> (raw)
In-Reply-To: <20070209122146.083e9ad8.rdunlap@xenotime.net>

Randy Dunlap wrote:
> On Thu, 1 Feb 2007 14:03:53 -0500 John W. Linville wrote:
> 
>> On Tue, Jan 30, 2007 at 03:39:44PM -0500, John W. Linville wrote:
>>> At the wireless summit in London, we collectively decided to move
>>> day-to-day wireless development discussions to our own list.  I am
>>> hosting a list for this purpose:
>>>
>>> 	http://lists.tuxdriver.org/mailman/listinfo/wireless
>> In response to some community requests, I have asked David
>> Miller to create a list for us on vger.kernel.org.  David has
>> obliged that request, so I have restricted new subscriptions to
>> wireless@lists.tuxdriver.org and I am asking everyone to move wireless
>> discussions to the new list.
>>
>> 	linux-wireless@vger.kernel.org
> 
> 
> This is Good.  Now I'd like to request that linux-wireless people set
> an example by not posting duplicates to netdev@vger.kernel.org also.  :)

I was trying to decide if I should post a question if there had been enough time for people to
switch. Now that the first complaint has been posted, I'm switched.

Larry

      reply	other threads:[~2007-02-09 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 20:39 New list for wireless dev discussions John W. Linville
     [not found] ` <20070201190353.GE5408@tuxdriver.com>
2007-02-09 20:21   ` Randy Dunlap
2007-02-09 21:00     ` Larry Finger [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=45CCE10A.3050109@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rdunlap@xenotime.net \
    /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).