linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dann frazier <dannf@dannf.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-parisc@vger.kernel.org, taggart@lackof.org, bame@riverrock.org
Subject: Re: decommissioning parisc-linux.org
Date: Tue, 14 Feb 2012 11:06:50 -0700	[thread overview]
Message-ID: <20120214180650.GC32602@dannf.org> (raw)
In-Reply-To: <1329076902.21613.52.camel@dabdike.int.hansenpartnership.com>

On Sun, Feb 12, 2012 at 02:01:42PM -0600, James Bottomley wrote:
> On Sun, 2012-02-12 at 08:49 -0600, James Bottomley wrote:
> > On Sun, 2012-02-12 at 08:38 -0600, James Bottomley wrote:
> > > On Wed, 2012-02-08 at 07:33 -0700, dann frazier wrote:
> > > > In the meantime, if anyone wants to get the website working on apache2
> > > > for the remainder of the system's lifetime, please let me know.
> > > > 
> > > I can probably do that.  At least the static part, since I run a bunch
> > > of apache 2 websites on my hosted system.
> > > 
> > > I've enabled it and put it up ... but it uses some type of server side
> > > scripting which I need to enable in the apache mods, so it's not
> > > entirely functional yet.
> > 
> > OK, done and up.
> > 
> > it was using SSI ... I haven't seen that for at least 20 years ...
> 
> I think I'm done.  I've got the three sites
> {www,ftp,hwdb}.parisc-linux.org up and running.  There aren't any more,
> are there (wiki seems to be eisee)?  Could someone also check the links
> to see that nothing's broken.

Good work!

      parent reply	other threads:[~2012-02-14 18:06 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
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 [this message]

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=20120214180650.GC32602@dannf.org \
    --to=dannf@dannf.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bame@riverrock.org \
    --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).