From: David Miller <davem@davemloft.net>
To: jeff@garzik.org
Cc: linville@tuxdriver.com, netdev@vger.kernel.org,
wireless@lists.tuxdriver.org
Subject: Re: New list for wireless dev discussions
Date: Tue, 30 Jan 2007 14:37:18 -0800 (PST) [thread overview]
Message-ID: <20070130.143718.89037193.davem@davemloft.net> (raw)
In-Reply-To: <45BFC854.4020507@garzik.org>
From: Jeff Garzik <jeff@garzik.org>
Date: Tue, 30 Jan 2007 17:36:04 -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
> >
> > If you are interested in Linux wireless development, please subscribe
> > to the list.
>
> Why move from vger?
>
> It seems much more sane to get postmaster@vger.kernel.org to create
> linux-wireless@vger.kernel.org list.
And we are happy to do so :-)
Just let me know.
next prev parent reply other threads:[~2007-01-30 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 20:39 New list for wireless dev discussions John W. Linville
2007-01-30 22:36 ` Jeff Garzik
2007-01-30 22:37 ` David Miller [this message]
2007-02-01 19:03 ` John W. Linville
2007-02-01 19:37 ` 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=20070130.143718.89037193.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=wireless@lists.tuxdriver.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).