From: Olaf Hering <olh@suse.de>
To: Arthur Othieno <apgo@patchbomb.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] drop linuxppc64-dev
Date: Wed, 18 Jan 2006 13:07:15 +0100 [thread overview]
Message-ID: <20060118120715.GB19765@suse.de> (raw)
In-Reply-To: <20060118110905.GA23678@krypton>
On Wed, Jan 18, Arthur Othieno wrote:
> What about the s/linuxppc64\.org/penguinppc\.org/g case? Or is
> penguinppc64.org preferable? Or am I just taking it too far? ;)
They are redirected on DNS or HTTP level.
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2006-01-18 12:07 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
2006-01-18 12:07 ` Olaf Hering [this message]
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=20060118120715.GB19765@suse.de \
--to=olh@suse.de \
--cc=apgo@patchbomb.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).