From: Ulf Carlsson <ulfc@thepuffingroup.com>
To: Ralf Baechle <ralf@uni-koblenz.de>
Cc: linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
linux-mips@vger.rutgers.edu
Subject: Re: CVS
Date: Sun, 13 Jun 1999 20:31:40 +0200 [thread overview]
Message-ID: <19990613203140.A8276@thepuffingroup.com> (raw)
In-Reply-To: <19990613185518.A11493@uni-koblenz.de>; from Ralf Baechle on Sun, Jun 13, 1999 at 06:55:23PM +0200
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
next prev parent reply other threads:[~1999-06-13 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-13 16:55 CVS Ralf Baechle
1999-06-13 18:31 ` Ulf Carlsson [this message]
1999-06-13 21:10 ` CVS Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
1999-09-30 21:15 CVS Ralf Baechle
1998-09-07 18:57 cvs Ulf Carlsson
1998-06-09 0:05 Swamped ralf
1998-06-09 19:19 ` cvs Ulf Carlsson
1998-06-09 19:34 ` cvs Alex deVries
1998-06-09 19:45 ` cvs Alex deVries
1998-06-09 20:51 ` cvs Mike Shaver
1998-06-10 20:04 ` cvs Mike Shaver
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=19990613203140.A8276@thepuffingroup.com \
--to=ulfc@thepuffingroup.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
/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