From: Denis Vlasenko <vda@ilport.com.ua>
To: "Carlos Martín" <carlos@cmartin.tk>
Cc: acx100-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: RFC: kill acx100-devel, migrate to netdev@vger.kernel.org
Date: Wed, 11 Jan 2006 10:50:52 +0200 [thread overview]
Message-ID: <200601111050.53028.vda@ilport.com.ua> (raw)
In-Reply-To: <200601110016.02120.carlos@cmartin.tk>
On Wednesday 11 January 2006 01:16, Carlos Martín wrote:
> On Tuesday 10 January 2006 07:29, Denis Vlasenko wrote:
> > Hi folks,
> >
> > Please read http://lkml.org/lkml/2006/1/5/671
> >
> > What about moving all acx development discussion
> > to netdev@vger.kernel.org?
>
> Sure, if the driver ships with mainline. Until it does, it would be OT here,
> IMO.
Jeff asked wireless folks to:
* Please CC wireless stack/driver discussions to netdev@vger.kernel.org
mailing list, rather than everybody hiding in their own little
corner.
I fully agree with him.
> > If yes, can acx100-devel address be automatically
> > redirected?
>
> If you'd like for people to still be able to use acx100-devel as before,
> you'd have to forward everything back and forth, and a discussion that started
> in netdev wouldn't have an easy way to get copied to acx100-devel unless it
> was manually CCd.
>
> I think it'd be easier just to tell people that discussion happens at netdev
> from now/whenever on.
Makes sense.
--
vda
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
next prev parent reply other threads:[~2006-01-11 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 6:29 RFC: kill acx100-devel, migrate to netdev@vger.kernel.org Denis Vlasenko
2006-01-10 23:16 ` Carlos Martín
2006-01-11 8:50 ` Denis Vlasenko [this message]
2006-01-11 9:34 ` Bas Vermeulen
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=200601111050.53028.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=acx100-devel@lists.sourceforge.net \
--cc=carlos@cmartin.tk \
--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).