From: Hollis Blanchard <hollis@penguinppc.org>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] drop linuxppc64-dev
Date: Mon, 16 Jan 2006 09:52:11 -0600 [thread overview]
Message-ID: <1137426731.22151.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20060116121244.GB7171@suse.de>
On Mon, 2006-01-16 at 13:12 +0100, Olaf Hering wrote:
> Everything is merged into arch/powerpc now.
> Stop cross-posting.
> --- linux-2.6.15-olh.orig/MAINTAINERS
> +++ linux-2.6.15-olh/MAINTAINERS
> @@ -527,7 +527,7 @@ S: Supported
> BROADBAND PROCESSOR ARCHITECTURE
> P: Arnd Bergmann
> M: arnd@arndb.de
> -L: linuxppc64-dev@ozlabs.org
> +L: linuxppc-dev@ozlabs.org
> W: http://linuxppc64.org
> S: Supported
Are you suggesting that nobody should ever use linuxppc64-dev now? If
so, patching MAINTAINERS doesn't seem like the right way to enforce
that.
Do we want to think about merging the mailing lists? Both seem fairly
high-volume right now (compare
http://ozlabs.org/pipermail/linuxppc64-dev/ and
http://ozlabs.org/pipermail/linuxppc-dev/). linuxppc-embedded is
separate. There are certainly lots of emails and patches that are common
to both 32- and 64-bit, though...
The subscriber lists don't overlap 100%, but the difference might be
small enough not to matter to many people.
-Hollis
next prev parent reply other threads:[~2006-01-16 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:12 [PATCH] drop linuxppc64-dev Olaf Hering
2006-01-16 15:52 ` Hollis Blanchard [this message]
2006-01-16 16:30 ` Olaf Hering
2006-01-18 11:09 ` Arthur Othieno
2006-01-18 12:07 ` Olaf Hering
2006-01-18 15:48 ` Hollis Blanchard
2006-01-18 18:53 ` [PATCH] powerpc: replace linuxppc64.org references with penguinppc.org/ppc64/ Arthur Othieno
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=1137426731.22151.8.camel@localhost.localdomain \
--to=hollis@penguinppc.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
/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.