From: "Martin J. Bligh" <mbligh@google.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Nigel Cunningham <nigel@nigel.suspend2.net>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: Who is administering the kernel bugzilla?
Date: Sat, 02 Jun 2007 11:15:34 -0700 [thread overview]
Message-ID: <4661B3C6.5040803@google.com> (raw)
In-Reply-To: <20070602155603.GE5500@stusta.de>
Adrian Bunk wrote:
> On Sat, Jun 02, 2007 at 01:42:06AM +0200, Rafael J. Wysocki wrote:
>> Hi,
>>
>> Can anyone please tell me who's administering the kernel bugzilla now?
>>
>> I've tried to write to bugme-admin@linux-foundation.org , but this address seems
>> to point to nowhere.
>> ...
>
> Martin Bligh (explicitely Cc'ed) should be able to help.
Yup, it does point somewhere, it's just an alias that bounces
one address ... I did get your request - will fix it.
M.
next prev parent reply other threads:[~2007-06-02 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 23:42 Who is administering the kernel bugzilla? Rafael J. Wysocki
2007-06-02 15:56 ` Adrian Bunk
2007-06-02 18:15 ` Martin J. Bligh [this message]
2007-06-02 21:35 ` Rafael J. Wysocki
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=4661B3C6.5040803@google.com \
--to=mbligh@google.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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