public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Collins Richey <erichey2@home.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Linux 1.0_rc5 status update
Date: Mon Jun 11 18:52:02 2001	[thread overview]
Message-ID: <20010611190058.6fa37b1f.erichey2@home.com> (raw)
In-Reply-To: <003801c0f2c9$0d6a9150$fd1942c3@bluescreen>

On Tue, 12 Jun 2001 00:51:26 +0200 "Mathijs Kwik" <troxx@segfault.nl>
wrote:

> Daniel and Achim and all other devs
> tnx again
> enjoy your vacation
> 
> 
> ----- Original Message -----
> From: "Daniel Robbins" <drobbins@gentoo.org>
> To: <gentoo-announce@gentoo.org>; <gentoo-dev@gentoo.org>
> Sent: Monday, June 11, 2001 9:16 PM
> Subject: [gentoo-dev] Gentoo Linux 1.0_rc5 status update
> 
> 
> > Hi All,
> >
> > Well, Gentoo Linux 1.0_rc5 is around the corner, but first... we need a
> > vacation. :)
> >
> > Achim has been working really hard on our Portage tree, and right now
> > everything builds perfectly and all known build problems have been
> fixed
> for
> > our ~700 packages (Thanks Achim!).  In addition, we now have a
> prototype
> boot
> > CD that actually works.  So, we are _very_ close to the Gentoo Linux
> 1.0_rc5
> > release; everything is falling into place.
> >
> > However, Achim is starting a new web company and has a lot of
> outstanding
> work
> > to complete; also, I have quite a few articles to write over here.  So,
> in
> > order to catch up on our consulting responsibilities, we'll be on
> "vacation"
> > from Gentoo Linux development for one week, starting today.  We'll
> resume
> work
> > on Gentoo Linux one week from now, on June 18th.  Since we have about
> one
> week
> > left of work before Gentoo Linux 1.0_rc5 is ready (mainly boot CD
> refinements
> > and package building), you can expect Gentoo Linux 1.0_rc5 to be
> released
> very
> > close to June 25th.  This date should be fairly accurate, since 95% of
> the
> > 1.0_rc5 work is already complete and is sitting on CVS, waiting to be
> built.
> >
> > Developers:
> >
> > Achim has tagged all the 1.0_rc5 stuff, so you can continue making
> improvements
> > to CVS without worry.  However, please try to hang out on #gentoo and
> answer
> > any gentoo-dev posts about your work (and any other questions, if you
> can.)
> >

I hope you both have a wonderful vacation - glueckliche Ferien!

For those of us who have already installed and are successfully running a
gentoo system, would we have any need to reinstall and go through all the
30+ hours of compiles to get back to where we are now?  Has anything
essential changed, other than having a more reliable boot cdrom and,
hopefully, error free ebuilds?


Thanks,
-- 
Collins Richey
Denver area
gentoo system



  reply	other threads:[~2001-06-12  0:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 13:17 [gentoo-dev] Gentoo Linux 1.0_rc5 status update Daniel Robbins
2001-06-11 16:44 ` Mathijs Kwik
2001-06-11 16:53 ` Mathijs Kwik
2001-06-11 18:52   ` Collins Richey [this message]
2001-06-11 19:59     ` Daniel Robbins
2001-06-12  9:02     ` blutgens
2001-06-12  4:36 ` vOiD
2001-06-12  9:03   ` blutgens

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=20010611190058.6fa37b1f.erichey2@home.com \
    --to=erichey2@home.com \
    --cc=gentoo-dev@cvs.gentoo.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