From: Grant Grundler <grundler@parisc-linux.org>
To: pageexec@freemail.hu
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] parisc-linux.org kernel
Date: Wed, 9 Apr 2003 23:50:03 -0600 [thread overview]
Message-ID: <20030410055003.GB21872@dsl2.external.hp.com> (raw)
In-Reply-To: <3E947323.14900.19F1E3AF@localhost>
On Wed, Apr 09, 2003 at 07:23:15PM +0200, pageexec@freemail.hu wrote:
> > > To willy's credit, he's attempted to merge 2.4 parisc changes upstream
> > > at least twice but was torpedo'd both times.
> >
> > i don`t want to know ;-)
>
> actually, i'd like to (feel free to answer off-list),
Once the 2.4.20-preX bk tree that willy was using as "parent"
was discarded by marcelo because of other bugs in patches.
Or marcelo wouldn't accept the patch because he had a -pre candidate
and didn't want to risk that. Just stuff like that.
> since for all the
> other archs grsec/PaX runs on we could compile a working kernel from the
> vanilla tree - it just seems a mystery why parisc is an exception (not
> blaming anyone, just would like to see it more clear).
As willy noted, parisc is not an exception. last time willy looked at
merging, the 2.4 diff was something like 2 or 3MB. I'd hope it's a bit
smaller since Alan Cox merge a bunch of stuff into his tree.
But I haven't looked if/when Marcelo picked any of that up.
For comparison, last I heard, the 2.5 diff is something like < 100KB.
grant
next prev parent reply other threads:[~2003-04-10 5:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 16:53 [parisc-linux] parisc-linux.org kernel Alexander Gabert
2003-04-08 16:58 ` Matthew Wilcox
2003-04-08 17:06 ` Alexander Gabert
2003-04-08 17:08 ` Matthew Wilcox
2003-04-09 5:49 ` Grant Grundler
2003-04-09 7:54 ` Alexander Gabert
2003-04-09 15:47 ` Grant Grundler
2003-04-09 17:23 ` pageexec
2003-04-09 17:40 ` Matthew Wilcox
2003-04-09 18:20 ` pageexec
2003-04-09 17:48 ` Matthew Wilcox
2003-04-10 5:50 ` Grant Grundler [this message]
2003-04-10 11:19 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 7:36 Berthold Gunreben
[not found] <20030410155223.GA5254@dsl2.external.hp.com>
2003-04-11 5:40 ` Joel Soete
2003-04-11 9:41 ` Joel Soete
2003-04-11 15:58 ` Grant Grundler
2003-04-12 20:30 ` Joel Soete
2003-04-14 12:13 ` Joel Soete
2003-04-14 11:39 ` Alan Cox
2003-04-14 13:53 ` Joel Soete
2003-04-14 15:42 ` Joel Soete
2003-04-15 16:32 ` Joel Soete
2003-04-15 15:54 ` Alan Cox
2003-04-15 16:41 ` Randolph Chung
2003-04-15 16:47 ` Matthew Wilcox
2003-04-15 16:52 ` Joel Soete
2003-04-14 14:18 ` Michael Wood
2003-04-14 11:52 Joel Soete
2003-04-14 11:54 ` Matthew Wilcox
2003-04-14 12:53 ` Joel Soete
2003-04-16 10:13 Joel Soete
2003-04-16 11:06 ` Alan Cox
2003-04-16 16:44 Joel Soete
2003-04-16 16:50 ` Matthew Wilcox
2003-04-18 8:17 Joel Soete
2003-04-18 11:40 ` Joel Soete
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=20030410055003.GB21872@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=pageexec@freemail.hu \
--cc=parisc-linux@parisc-linux.org \
/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