linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: apgo@patchbomb.org (Arthur Othieno)
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] drop linuxppc64-dev
Date: Wed, 18 Jan 2006 06:09:05 -0500	[thread overview]
Message-ID: <20060118110905.GA23678@krypton> (raw)
In-Reply-To: <20060116121244.GB7171@suse.de>

On Mon, Jan 16, 2006 at 01:12:44PM +0100, Olaf Hering wrote:
> 
> Everything is merged into arch/powerpc now.
> Stop cross-posting.
> 
> Signed-off-by: Olaf Hering <olh@suse.de>
> 
>  Documentation/powerpc/hvcs.txt |    2 +-
>  MAINTAINERS                    |    4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)

[snip]

> Index: linux-2.6.15-olh/MAINTAINERS
> ===================================================================
> --- 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
>  
> @@ -1606,7 +1606,7 @@ P:	Anton Blanchard
>  M:	anton@samba.org
>  M:	anton@au.ibm.com
>  W:	http://linuxppc64.org
> -L:	linuxppc64-dev@ozlabs.org
> +L:	linuxppc-dev@ozlabs.org
>  S:	Supported
>  
>  LINUX SECURITY MODULE (LSM) FRAMEWORK

What about the s/linuxppc64\.org/penguinppc\.org/g case? Or is
penguinppc64.org preferable? Or am I just taking it too far? ;)

  parent reply	other threads:[~2006-01-18 11:32 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
2006-01-16 16:30   ` Olaf Hering
2006-01-18 11:09 ` Arthur Othieno [this message]
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=20060118110905.GA23678@krypton \
    --to=apgo@patchbomb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).