public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false•org>
To: Ppc Developers <linuxppc-dev@lists•linuxppc.org>
Subject: Re: irc.openprojects.net?
Date: Wed, 15 Jan 2003 11:09:06 -0500	[thread overview]
Message-ID: <20030115160906.GA17181@nevyn.them.org> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFOEOJEAAA.acurtis@onz.com>


On Wed, Jan 15, 2003 at 07:56:49AM -0800, Allen Curtis wrote:
>
> Does anyone know what happened to this IRC site? This URL does not resolve.
> Has #mklinux moved to a new server? I checked on irc.oftc.net but it looked
> pretty dead.

They decided to change their name again.  Try irc.freenode.net.

--
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-01-15 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 15:56 irc.openprojects.net? Allen Curtis
2003-01-15 16:09 ` Daniel Jacobowitz [this message]
2003-01-15 16:09 ` irc.openprojects.net? Momchil Velikov
     [not found] <NCBBIINEHIPFGJPLBEIFCEOKEAAA.acurtis@onz.com>
2003-01-15 16:05 ` irc.openprojects.net? Mark Hatle

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=20030115160906.GA17181@nevyn.them.org \
    --to=drow@false$(echo .)org \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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