public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@parthus.com>
To: "Bart Veer" <bartv@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] next release time
Date: Fri, 07 Jul 2000 09:21:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0007071708090.12490-100000@platinum.limerick.sslinc.com> (raw)
In-Reply-To: <200007071507.QAA20689@sheesh.cygnus.co.uk>

Hi,
	Thanks for this information, I remembered a local system that I'm
involved with having a scheme for doing CVS->FTP snapshots so I've added
ecos to the list of sites that are snapshotted with the system they use,

So you can now get daily snapshots (only taken when something
changes) from:

ftp://ftp.skynet.ie/cvs/

The snapshot tar file is 

ftp://ftp.skynet.ie/cvs/ecos-000707.tar.gz
and the files are in 
ftp://ftp.skynet.ie/cvs/ecos/

Please feel free to send any comments or improvements on this service to
me, I'll pass them on to the ftp site admin.

Regards,
	Dave.


> There are alternative approaches, e.g. developer snapshots, or only
> doing QA on "key" targets (which is what the gcc folks do for their
> major releases). For now anonymous CVS seems to be sufficient for most
> people, but this may change in future.
> 
> Of course there is nothing to stop other people from generating
> developer snapshots based on an anoncvs checkout, and writing the
> appropriate scripts. eCos is open source, so you are allowed to
> redistribute it yourself. If such developer snapshots proved to be
> popular with the community then we could start using the same scripts
> on sourceware.cygnus.com
> 
> Bart Veer // eCos net maintainer
> 

-- 
      David Airlie, Software Engineer, Parthus Technologies plc.,
       Mary Rosse Centre, National Tech Park, Limerick, Ireland.
   t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com

      reply	other threads:[~2000-07-07  9:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-07  7:49 Dave Airlie
2000-07-07  8:07 ` Bart Veer
2000-07-07  9:21   ` Dave Airlie [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=Pine.LNX.4.21.0007071708090.12490-100000@platinum.limerick.sslinc.com \
    --to=airlied@parthus.com \
    --cc=bartv@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.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).