linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dann frazier <dannf@dannf.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Thibaut VARENE <T-Bone@parisc-linux.org>,
	John David Anglin <dave.anglin@bell.net>,
	linux-parisc List <linux-parisc@vger.kernel.org>,
	taggart@lackof.org, bame@riverrock.org
Subject: Re: decommissioning parisc-linux.org
Date: Wed, 23 Jan 2013 14:17:39 -0700	[thread overview]
Message-ID: <20130123211739.GA26674@dannf.org> (raw)
In-Reply-To: <CADZpyiwqn60ChBSO5PJj9AojH2CWQvRgjYM61iRQxryH2wzUnA@mail.gmail.com>

On Tue, Feb 14, 2012 at 01:33:48PM -0500, Carlos O'Donell wrote:
> On Tue, Feb 14, 2012 at 1:31 PM, Thibaut VARENE <T-Bone@parisc-linux.org> wrote:
> > It looks to me like this burden clearly outweighs the benefits of
> > being selfhosted, so maybe the right move is to use a supported
> > architecture for hosting the website? Given the "audience" for
> > linux-parisc, I don't think it would make a significant difference...
> 
> I tend to agree. Use the right tool for the right job.
> 
> Fun hacking = HPPA.
> 
> Serve the website = x86.

fyi, the subnet on which palinux (aka parisc-linux.org) is hosted will
be going away at the end of February. This sounds like a good target
date for the move :)

  reply	other threads:[~2013-01-23 21:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 14:33 decommissioning parisc-linux.org dann frazier
2012-02-08 22:16 ` Thibaut VARENE
2012-02-08 23:47   ` John David Anglin
2012-02-09  1:53     ` John David Anglin
2012-02-09 14:54       ` John David Anglin
2012-02-09 15:41         ` Paul Bame
2012-02-09 17:55     ` dann frazier
2012-02-11 19:11       ` John David Anglin
2012-02-11 22:12         ` Thibaut VARENE
2012-02-11 22:41           ` John David Anglin
2012-02-11 23:26             ` Thibaut VARENE
2012-02-11 23:29             ` Carlos O'Donell
2012-02-12  0:25               ` John David Anglin
2012-02-14 18:05         ` dann frazier
2012-02-14 18:31           ` Thibaut VARENE
2012-02-14 18:33             ` Carlos O'Donell
2013-01-23 21:17               ` dann frazier [this message]
2013-01-23 23:14                 ` John David Anglin
2013-01-23 23:32                   ` dann frazier
2012-02-09 17:56   ` dann frazier
2012-02-09 19:18     ` Martin K. Petersen
2012-02-09 20:49       ` dann frazier
2012-02-12 14:38 ` James Bottomley
2012-02-12 14:49   ` James Bottomley
2012-02-12 20:01     ` James Bottomley
2012-02-12 22:47       ` Carlos O'Donell
2012-02-12 22:56         ` John David Anglin
2012-02-13  2:22           ` Carlos O'Donell
2012-02-13  5:20             ` James Bottomley
2012-02-13 22:26           ` Carlos O'Donell
2012-02-13  4:05       ` Grant Grundler
2012-02-13  5:19         ` James Bottomley
2012-02-14 18:06         ` dann frazier
2012-02-13 11:23       ` Thibaut VARENE
2012-02-14 13:41         ` Thibaut VARENE
2012-02-14 18:06       ` dann frazier

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=20130123211739.GA26674@dannf.org \
    --to=dannf@dannf.org \
    --cc=T-Bone@parisc-linux.org \
    --cc=bame@riverrock.org \
    --cc=carlos@systemhalted.org \
    --cc=dave.anglin@bell.net \
    --cc=linux-parisc@vger.kernel.org \
    --cc=taggart@lackof.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).