All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] wireless-regdb: Update keys and maintainer information
Date: Fri, 5 Dec 2014 13:04:58 -0600	[thread overview]
Message-ID: <20141205190458.GD40007@ubuntu-hedt> (raw)
In-Reply-To: <20141205163134.GC13629@ubuntu-mba51>

On Fri, Dec 05, 2014 at 10:31:34AM -0600, Seth Forshee wrote:
> As announced by John [1], I'm taking over maintaintership of the
> wireless regulatory databse. Make it official by adding my key,
> removing John's, and updating the Makefile and documentation to
> reflect the change in maintainer.
> 
> [1] http://permalink.gmane.org/gmane.linux.kernel.wireless.general/131573

Also I should point out that the new location for the git repo is:

 git://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git

I'll be sending patches shortly to update this in the kernel
documentation and in CRDA.

Seth

WARNING: multiple messages have this Message-ID (diff)
From: Seth Forshee <seth.forshee@canonical.com>
To: wireless-regdb@lists.infradead.org, linux-wireless@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [wireless-regdb] [PATCH] wireless-regdb: Update keys and maintainer information
Date: Fri, 5 Dec 2014 13:04:58 -0600	[thread overview]
Message-ID: <20141205190458.GD40007@ubuntu-hedt> (raw)
In-Reply-To: <20141205163134.GC13629@ubuntu-mba51>

On Fri, Dec 05, 2014 at 10:31:34AM -0600, Seth Forshee wrote:
> As announced by John [1], I'm taking over maintaintership of the
> wireless regulatory databse. Make it official by adding my key,
> removing John's, and updating the Makefile and documentation to
> reflect the change in maintainer.
> 
> [1] http://permalink.gmane.org/gmane.linux.kernel.wireless.general/131573

Also I should point out that the new location for the git repo is:

 git://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git

I'll be sending patches shortly to update this in the kernel
documentation and in CRDA.

Seth

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


  parent reply	other threads:[~2014-12-05 19:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 16:31 [PATCH] wireless-regdb: Update keys and maintainer information Seth Forshee
2014-12-05 16:31 ` [wireless-regdb] " Seth Forshee
2014-12-05 16:33 ` John W. Linville
2014-12-05 16:33   ` [wireless-regdb] " John W. Linville
2014-12-05 16:47   ` Seth Forshee
2014-12-05 16:47     ` [wireless-regdb] " Seth Forshee
2014-12-05 18:55     ` Arend van Spriel
2014-12-05 18:55       ` [wireless-regdb] " Arend van Spriel
2014-12-05 18:59       ` Seth Forshee
2014-12-05 18:59         ` [wireless-regdb] " Seth Forshee
2014-12-05 19:04 ` Seth Forshee [this message]
2014-12-05 19:04   ` Seth Forshee
  -- strict thread matches above, loose matches on Subject: below --
2023-12-01  7:50 Chen-Yu Tsai
2023-12-01  7:54 Chen-Yu Tsai
2023-12-01 15:13 ` Seth Forshee

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=20141205190458.GD40007@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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.