cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: cpufreq@lists.linux.org.uk
Subject: Re: list moving.
Date: Thu, 31 Jul 2008 18:21:44 -0400	[thread overview]
Message-ID: <20080731222144.GH29139@codemonkey.org.uk> (raw)
In-Reply-To: <20080730162628.GI2361@codemonkey.org.uk>

On Wed, Jul 30, 2008 at 12:26:29PM -0400, Dave Jones wrote:
 > Given that the spam problem on this list is getting really out of hand,
 > I'm giving thought to the idea of asking davem to host a new list
 > on vger.kernel.org
 > 
 > Unless there's any objection over the next few days, I'll make
 > arrangements, and change the default bugzilla destination etc.

Ok. cpufreq@vger.kernel.org has been created.

Send 'subscribe cpufreq' in the body of the mail to 'majordomo@vger.kernel.org'
to join up. 

	Dave

-- 
http://www.codemonkey.org.uk

  parent reply	other threads:[~2008-07-31 22:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 16:26 list moving Dave Jones
2008-07-30 20:20 ` Russell King
2008-07-31 22:21 ` Dave Jones [this message]
2008-08-01  8:36   ` Russell King
2008-08-01  8:48     ` Dominik Brodowski
2008-08-01 10:00       ` Russell King
2008-08-02 19:03         ` Cesar Eduardo Barros
2008-08-02 20:13           ` Russell King

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=20080731222144.GH29139@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=cpufreq@lists.linux.org.uk \
    /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