All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [ANN] wireless-regdb: master-2013-10-11
Date: Fri, 11 Oct 2013 16:39:01 -0400	[thread overview]
Message-ID: <20131011203901.GA23477@tuxdriver.com> (raw)
In-Reply-To: <20131011202459.GF14329@tuxdriver.com>

On Fri, Oct 11, 2013 at 04:24:59PM -0400, John W. Linville wrote:
> (Cutting the short log, since the original version got classified as
> SPAM on vger.kernel.org...??)
> 
> A new release of wireless-regdb (master-2013-10-11) is available at:
> 
> http://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2013.10.11.tar.gz
> 
> Here is the short log of the changes included since the 2013-02-13
> release:
> 
> SNIP -- you'll have to check it yourself:
> 
> 	git log master-2013-02-13..master-2013-10-11 | git shortlog

FYI -- I've purged my folders of all other old/pending wireless-regdb
stuff.  If you have a change that you still want to propose to the
regulatory database, please send it as a _patch_ at your leisure.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org
Subject: Re: [wireless-regdb] [ANN] wireless-regdb: master-2013-10-11
Date: Fri, 11 Oct 2013 16:39:01 -0400	[thread overview]
Message-ID: <20131011203901.GA23477@tuxdriver.com> (raw)
In-Reply-To: <20131011202459.GF14329@tuxdriver.com>

On Fri, Oct 11, 2013 at 04:24:59PM -0400, John W. Linville wrote:
> (Cutting the short log, since the original version got classified as
> SPAM on vger.kernel.org...??)
> 
> A new release of wireless-regdb (master-2013-10-11) is available at:
> 
> http://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2013.10.11.tar.gz
> 
> Here is the short log of the changes included since the 2013-02-13
> release:
> 
> SNIP -- you'll have to check it yourself:
> 
> 	git log master-2013-02-13..master-2013-10-11 | git shortlog

FYI -- I've purged my folders of all other old/pending wireless-regdb
stuff.  If you have a change that you still want to propose to the
regulatory database, please send it as a _patch_ at your leisure.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

_______________________________________________
wireless-regdb mailing list
wireless-regdb@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wireless-regdb


  reply	other threads:[~2013-10-11 20:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 20:24 [ANN] wireless-regdb: master-2013-10-11 John W. Linville
2013-10-11 20:24 ` [wireless-regdb] " John W. Linville
2013-10-11 20:39 ` John W. Linville [this message]
2013-10-11 20:39   ` John W. Linville
2013-10-31 23:32 ` Thomas Bächler
2013-11-04 19:18   ` John W. Linville
2013-11-20 10:29     ` Luis R. Rodriguez
2013-11-20 16:25       ` John W. Linville
2013-11-20 16:47         ` John W. Linville
2013-11-20 18:08           ` Thomas Bächler

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=20131011203901.GA23477@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wireless-regdb@lists.infradead.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.