Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Ryan Rafferty <rraffer1@osf1.gmu.edu>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu
Subject: Re: Snapshot
Date: Tue, 7 Dec 1999 09:11:01 -0200	[thread overview]
Message-ID: <19991207091101.A759@uni-koblenz.de> (raw)
In-Reply-To: <Pine.OSF.3.96.991206221350.25177A-100000@osf1.gmu.edu>

On Mon, Dec 06, 1999 at 10:14:12PM -0500, Ryan Rafferty wrote:

> Any highlights about important changes present in this snapshot?

Most important for you guys out there the upgrade to 2.3.21 and a number
of bug fixes.  Try it, break it.  Again ;-)  Aside of this this kernel
also has a good part of the 64-bit stuff.  Not all of it, I'm maintaining
the 32-bit kernel, the Indy 64-bit and the Origin kernel as separate
trees to prevent bugs from creeping from on tree in the other.

> On Mon, 6 Dec 1999, Ralf Baechle wrote:
> 
> > I've put a snapshot of current CVS kernel sources into
> > oss.sgi.com:/pub/linux/mips/src/kernel/linux-19991206.tar.gz.

  parent reply	other threads:[~1999-12-07 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-06 23:44 Snapshot Ralf Baechle
1999-12-07  5:07 ` Snapshot A. Wrasman
     [not found] ` <Pine.OSF.3.96.991206221350.25177A-100000@osf1.gmu.edu>
1999-12-07 11:11   ` Ralf Baechle [this message]
1999-12-09 15:49 ` Snapshot Florian Lohoff
1999-12-09 19:02   ` Snapshot Ralf Baechle
1999-12-09 21:00   ` Snapshot Harald Koerfgen
1999-12-21 12:02 ` patch for glibc-2.0.6 Jun Matsuda
1999-12-21 14:19   ` Ralf Baechle
1999-12-21 23:59     ` Jun Matsuda
1999-12-21 15:54   ` Florian Lohoff
  -- strict thread matches above, loose matches on Subject: below --
1999-12-07 20:05 Snapshot Mike Hill
1999-12-09 22:41 ` Snapshot Andrew R. Baker

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=19991207091101.A759@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=rraffer1@osf1.gmu.edu \
    /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