Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Alexander Gabert <pappy@nikita.ath.cx>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] parisc-linux.org kernel
Date: Tue, 8 Apr 2003 18:08:39 +0100	[thread overview]
Message-ID: <20030408170839.GC23430@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030408170612.GA15497@nikita.ath.cx>

On Tue, Apr 08, 2003 at 07:06:12PM +0200, Alexander Gabert wrote:
> i am asking because of www.grsecurity.net
> 
> i am tired defeating hunks they are putting in because they
> work in arch/parisc on the vanilla kernel.org kernel.
> 
> can't you talk to them and convince them to use "our" parisc-linux image
> for the grsecurity parisc patches in the future?

perhaps you should talk to them.  tell them to work against the patches
in http://www.kernel.org/linux/kernel/ports/parisc/v2.4/

> if it would only be a matter of months when both kernels merge, it would
> not be necessary.
> but i don`t want to spend my time messing with patches when i can do
> better things ...

bits and pieces are being merged from the parisc tree into marcelo's tree,
but it's just not worth fighting to get this stuff merged.  we're mostly
merged for 2.5 and i'd rather spend my time working on that.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-04-08 17:08 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 [this message]
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
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=20030408170839.GC23430@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=pappy@nikita.ath.cx \
    --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