From: Dave Jones <davej@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Németh Márton" <nm127@freemail.hu>,
cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: correct broken links and email address
Date: Thu, 9 Oct 2008 13:50:04 -0400 [thread overview]
Message-ID: <20081009175004.GB20608@redhat.com> (raw)
In-Reply-To: <20081009142215.605f757c@lxorguk.ukuu.org.uk>
On Thu, Oct 09, 2008 at 02:22:15PM +0100, Alan Cox wrote:
> On Thu, 09 Oct 2008 14:59:17 +0200
> Németh Márton <nm127@freemail.hu> wrote:
>
> > From: Márton Németh <nm127@freemail.hu>
> >
> > Replace the no longer working links and email address in the
> > documentation and in source code.
> >
> > Signed-off-by: Márton Németh <nm127@freemail.hu>
>
> Someone needs to update the bugzilla addresses for cpufreq bugs too I
> think..
I did that when the list moved.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2008-10-09 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 9:35 [PATCH] cpufreq: correct broken links and email address Németh Márton
2008-10-09 12:59 ` Németh Márton
2008-10-09 13:22 ` Alan Cox
2008-10-09 17:50 ` Dave Jones [this message]
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=20081009175004.GB20608@redhat.com \
--to=davej@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm127@freemail.hu \
/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.