From: Mike Shaver <shaver@netscape.com>
To: hppa-linux@puffingroup.com
Subject: [hppa-linux] kernel stuff
Date: Wed, 17 Mar 1999 21:14:07 -0500 [thread overview]
Message-ID: <36F0616F.D8B86BAD@netscape.com> (raw)
Two questions:
1) Why is there not a complete kernel checked into CVS? It's going to
be a major nightmare if we don't control the entire tree and when we
merge forward to new Linus versions, etc.
[shaver@loonie parisc-linux]$ cvs -d
:pserver:shaver@sod.res.cmu.edu:/home/cvs/hppa co linux
cvs server: Updating linux
cvs server: Updating linux/arch
cvs server: Updating linux/arch/parisc
cvs server: Updating linux/arch/parisc/hp
U linux/arch/parisc/hp/machines.h
cvs server: Updating linux/arch/parisc/hp/boot
U linux/arch/parisc/hp/boot/Makefile
U linux/arch/parisc/hp/boot/mkipl.c
U linux/arch/parisc/hp/boot/mklifhdr.c
[shaver@loonie parisc-linux]$
2) What version should I unpack under the bits that _are_ in the tree?
Mike
--
291958.32 246858.49
reply other threads:[~1999-03-18 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=36F0616F.D8B86BAD@netscape.com \
--to=shaver@netscape.com \
--cc=hppa-linux@puffingroup.com \
/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