From: Tony Breeds <tony@bakeyournoodle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linuxppc-dev@ozlabs.org, anton@samba.org
Subject: Re: [Bugme-new] [Bug 11027] New: random forward time jumps
Date: Fri, 4 Jul 2008 11:50:22 +1000 [thread overview]
Message-ID: <20080704015022.GV20457@bakeyournoodle.com> (raw)
In-Reply-To: <20080703175932.53ec7151.akpm@linux-foundation.org>
On Thu, Jul 03, 2008 at 05:59:32PM -0700, Andrew Morton wrote:
> Nope, the only account matching .*ppc.* and .*power.* is
> platform_ppc-32@kernel-bugs.osdl.org. (I have elevated bugzilla perms
> so I can can query the users list) (everyone should have this - it's
> handy).
>
> There is a category "Platform Specific/Hardware"/PPC-64. Those go to
> anton@samba.org.
Can you get this changed to platform_ppc-64@kernel-bugs.osdl.org
(obvisouly this'll need to be created)?
> There is a category "Platform Specific/Hardware"/PPC-62. Those go to
> platform_ppc-32@kernel-bugs.osdl.org.
>
> So setting a watch on both those accounts would suit.
Then the linuxppc-dev "person" can watch both of them. Seems slightly
more "offical".
> Or you can just ignore it all. I screen all bugzilla reports and will
> ensure that suitable people know about them.
Yeah we could but it'd be easier for you if we didn't :)
Yours Tony
linux.conf.au http://www.marchsouth.org/
Jan 19 - 24 2009 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2008-07-04 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11027-10286@http.bugzilla.kernel.org/>
2008-07-02 18:06 ` [Bugme-new] [Bug 11027] New: random forward time jumps Andrew Morton
2008-07-04 0:46 ` Michael Ellerman
2008-07-04 0:59 ` Andrew Morton
2008-07-04 1:50 ` Tony Breeds [this message]
2008-07-04 1:54 ` Michael Ellerman
2008-07-04 3:32 ` Grant Likely
2008-07-07 11:12 ` Josh Boyer
2008-07-04 2:02 ` Andrew Morton
2008-08-18 4:24 ` Tony Breeds
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=20080704015022.GV20457@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.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.