Swamped ...

Swamped ...

[ralf]

Hi all,

as some you guys may know currently there is Linux the Linux/UNIX
conference season.  I'm currently pretty burried upto my throat in
email, so please excuse if I didn't answer your email yet.

  Ralf

cvs

[Ulf Carlsson]

Hi,
Can't you please make a tarball of the latest kernel in the cvs tree and
put it in /pub/test or something?

- Ulf

Re: cvs

[Alex deVries]

Ulf,

You want:

ftp://ftp.linux.sgi.com:/pub/mips-linux/GettingStarted/vmlinux-indy-2.1.99.tar.gz.

(Oh, and I have most of the RH installer running... more updates later
today)

- A

-- 
Alex deVries, puffin on LinuxNet.
http://www.engsoc.carleton.ca/~adevries/ .


On Tue, 9 Jun 1998, Ulf Carlsson wrote:

> Date: Tue, 9 Jun 1998 21:19:56 +0200 (CEST)
> From: Ulf Carlsson <grimsy@zigzegv.ml.org>
> To: linux@cthulhu.engr.sgi.com
> Subject: cvs
> 
> Hi,
> Can't you please make a tarball of the latest kernel in the cvs tree and
> put it in /pub/test or something?
> 
> - Ulf
> 

Re: cvs

[Alex deVries]

On Tue, 9 Jun 1998, Ulf Carlsson wrote:
> Hi,
> Can't you please make a tarball of the latest kernel in the cvs tree and
> put it in /pub/test or something?

Ooops, you meant _source_, I read _binary_, sorry.

Uh, why not just use cvs to check it out?

- A

Re: cvs

[Mike Shaver]

Alex deVries wrote:
> Uh, why not just use cvs to check it out?

Because I'm lamer than lame and still haven't made anonymous cvs work
right.

I'll do that right now...

Mike

-- 
107190.57 88319.77

Re: cvs

[Mike Shaver]

Mike Shaver wrote:
> I'll do that right now...

And I did (almost right away, even!).

cvs -d :pserver:cvs@linus.linux.sgi.com:/cvs login
(password is "cvs")
cvs -d :pserver:cvs@linus.linux.sgi.com:/cvs co linux

Although CVS doesn't appear to be honouring the CVSROOT/readers file,
:pserver: checkins don't succeed because there's no /var/tmp in the
chroot'd area.  Not optimal, but it keeps things safe for now.

Mike

-- 
190678.54 157843.71

cvs

[Ulf Carlsson]

What happend to the CVS ChangeLog? It hasn't been modified since 98/06/15.
Quite handy thing otherwise.

- Ulf

CVS

[Ralf Baechle]

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.

  Ralf

Re: CVS

[Ulf Carlsson]

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?

- Ulf

Re: CVS

[Ralf Baechle]

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

CVS

[Ralf Baechle]

Could those with write access to the CVS archive please hold their patches
back until I've commited 2.3.18 or send mail them to me?  It'll make myself
life easier as I'm currently with several source trees which I have to
merge into a single one.  Thanks,

  Ralf