From: David Huggins-Daines <dhd@linuxcare.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Branching "stable" 2.3.99pre8 kernel
Date: 01 Sep 2000 15:41:55 -0400 [thread overview]
Message-ID: <87r973lx18.fsf@linuxcare.com> (raw)
Hi,
As some people have probably heard me say in person, the current head
branch of the kernel CVS tree is a substantial step backwards in speed
and now stability from 2.3.99pre8, and is not really usable for me to
do any user-space work on.
My 2.3.99pre8 tree (see below) crashes *repeatably* and
*deterministically* (with the exception of NFS which is basically crap
anyway), and therefore I'm fixing them as I find them. In contrast,
what we've got at the head of our CVS crashes *randomly* on my A180
and will not stay up long enough to run the configure script of any of
the programs I have successfully built natively on 2.3.99pre8.
I don't know whether this is because 2.4.0test5 is broken upstream, or
whether we screwed up the merge, but it is simply unusable for my
purposes.
Therefore, until it gets fixed, I am using a hacked-up combination of
the pre-merge 2.3.99pre8 and updated signal and trap handling code. I
would like to tag this as a branch in CVS so that I can continue to
fix kernel bugs that affect me without having to fully update to 2.4.0.
Will people mind terribly if I do this? It should be trivial to merge
changes from the branch as needed.
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next reply other threads:[~2000-09-01 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 19:41 David Huggins-Daines [this message]
2000-09-01 20:00 ` [parisc-linux] Branching "stable" 2.3.99pre8 kernel Grant Grundler
2000-09-01 22:27 ` David Huggins-Daines
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=87r973lx18.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=parisc-linux@thepuffingroup.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