From: Gary Thomas <gary@mlbassoc.com>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: [ECOS] How to build redboot/ecos?
Date: Mon, 22 Sep 2003 16:29:00 -0000 [thread overview]
Message-ID: <1064248165.1015.308.camel@hermes> (raw)
In-Reply-To: <3F6F2048.9070906@ecoscentric.com>
On Mon, 2003-09-22 at 10:16, Alex Schuilenburg wrote:
> Gary Thomas wrote:
> ...
> >>>Really? Where? The only official source for eCos is:
> >>> http://sources.redhat.com/ecos/
> >>
> >>It is?
> >>
> >>I thought we were moving away from the RedHat based URL to the vendor
> >>neutral http://ecos.sourceware.org/
> >
> >
> > Fair enough, but it surely isn't on sourceforge AFAIK.
>
> Source*ware*, not sourceforge.
>
> ecos.sourceware.org is simply an alias for s.r.c. and s.r.c. has been
> set up to provide virtual hosting. Hence it is the same machine, just
> not advertised as such. The gcc group use the same trick for gcc.gnu.org
>
> I suspect the announcement may have been be delayed until eCos falls
> under the FSF umbrella so that ecos becomes also available as
> http://ecos.gnu.org. The prefferred "official" URL,
> ecos.gnu.org or ecos.sourceware.org, is up to you maintainers to decide :-)
>
Understood. I was just seeing if this guy actually got something from
sourceforge (some clandestine project?) or was just confused.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next prev parent reply other threads:[~2003-09-22 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A4E787A2467EF849B00585F14C900559068B13@18.172.in-addr.arpa>
[not found] ` <1063752622.5547.472.camel@hermes>
2003-09-22 15:56 ` Alex Schuilenburg
2003-09-22 16:07 ` Gary Thomas
2003-09-22 16:20 ` Alex Schuilenburg
2003-09-22 16:29 ` Gary Thomas [this message]
2003-09-22 16:32 ` Jonathan Larmour
2003-09-22 16:35 ` Gary Thomas
2003-09-22 17:03 ` Jonathan Larmour
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=1064248165.1015.308.camel@hermes \
--to=gary@mlbassoc.com \
--cc=alexs@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
/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).