linux-mips
[Top] [All Lists]

Re: CVS

To: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
Subject: Re: CVS
From: Ralf Baechle <ralf@uni-koblenz.de>
Date: Sun, 13 Jun 1999 23:10:13 +0200
In-reply-to: <19990613203140.A8276@thepuffingroup.com>; from Ulf Carlsson on Sun, Jun 13, 1999 at 08:31:40PM +0200
References: <19990613185518.A11493@uni-koblenz.de> <19990613203140.A8276@thepuffingroup.com>
Sender: owner-linux@cthulhu.engr.sgi.com
On Sun, Jun 13, 1999 at 08:31:40PM +0200, Ulf Carlsson wrote:

> On Sun, Jun 13, 1999 at 06:55:23PM +0200, Ralf Baechle wrote:
> > I've just commited Linux 2.2.8 into the CVS archive.  Once this is
> > finished I'll create a branch named linux_2_2 for the 2.2 development
> > in the archive.  If you just do ``cvs update'' you'll stay on the
> > mainline of the development, that is 2.3.  If you want to work with
> > the 2.2 sources then you'll have to add the option ``-r linux_2_2''
> > to your next cvs update or cvs co command.
> > 
> > I'm already running 2.2.9 and 2.3.1 on my Indy but the checkin is that
> > slow that I won't commit these versions into the CVS archive now.
> 
> I would appreciate if it was possible to continue using 32 bit code on the 
> Indy,
> even if you add 64 bit code. Maybe we can add it as an option in the kernel
> configuration scripts?

I'll implement MIPS64 as a new architecture just like sparc64 is different
from sparc.  The changes are too big and I finally want to use the
freedem to use all the tricks in the box.  It also means that we'll have
some more of a maintenance pain for the common code for mips and mips64.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>
  • CVS, Ralf Baechle
    • Re: CVS, Ulf Carlsson
      • Re: CVS, Ralf Baechle <=