linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] drop linuxppc64-dev
Date: Mon, 16 Jan 2006 17:30:35 +0100	[thread overview]
Message-ID: <20060116163035.GA13973@suse.de> (raw)
In-Reply-To: <1137426731.22151.8.camel@localhost.localdomain>

 On Mon, Jan 16, Hollis Blanchard wrote:

> 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.

It felt like a good starting point for this kind of discussion. :-)

-- 
short story of a lazy sysadmin:
 alias appserv=wotan

  reply	other threads:[~2006-01-16 16:30 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 [this message]
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=20060116163035.GA13973@suse.de \
    --to=olh@suse.de \
    --cc=hollis@penguinppc.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 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).