From: Jonathan Larmour <jifl@jifvik.org>
To: "David N. Welton" <davidw@dedasys.com>
Cc: Gary Thomas <gary@chez-thomas.org>,
"ecos-discuss (E-Mail)" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] patches reviewed?
Date: Thu, 20 Jun 2002 18:32:00 -0000 [thread overview]
Message-ID: <3D128215.BE177E1F@jifvik.org> (raw)
In-Reply-To: <87n0tpd4eb.fsf@dedasys.com>
"David N. Welton" wrote:
>
> Gary Thomas <gary@chez-thomas.org> writes:
>
> > Sorry for the problems (those lists are out of our hands)
>
> Is it time for an infrastructure change, at this point?
It could be argued. However there's a lot of history with the current
setup. And of course sources.redhat.com provides a lot of infrastructure
and resources that we'd need to duplicate and pay for.... and without a
company behind it it's more difficult. Unless we moved to SourceForge or
similar.
> I would suggest, for one thing, grabbing a good hostname that can be
> used to host a web page, even if the provider/hosting service switches
> around.
All the good domains are taken of course :-). Although we have a few ideas
which we could use if we did decide to move after all. I won't mention them
to prevent domain squatting.
Jifl
--
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-06-21 1:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 10:46 Koeller, T.
2002-06-20 11:05 ` Jonathan Larmour
2002-06-20 13:35 ` Gary Thomas
2002-06-20 14:26 ` David N. Welton
2002-06-20 18:32 ` Jonathan Larmour [this message]
2002-06-20 18:28 ` Jonathan Larmour
2002-06-21 1:21 ` Holger Schurig
2002-06-20 15:32 James Dabbs
2002-06-20 15:43 ` David N. Welton
2002-06-20 15:51 ` Scott Dattalo
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=3D128215.BE177E1F@jifvik.org \
--to=jifl@jifvik.org \
--cc=davidw@dedasys.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@chez-thomas.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 read-only IMAP folder(s) and NNTP newsgroup(s).