From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] parisc-linux.org kernel
Date: Thu, 10 Apr 2003 12:19:26 +0100 [thread overview]
Message-ID: <20030410111926.GR23430@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030410055003.GB21872@dsl2.external.hp.com>
On Wed, Apr 09, 2003 at 11:50:03PM -0600, Grant Grundler wrote:
> > 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.
And other people were patching things in the parisc-specific directories
which conflicted with my patches ;-(
> 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.
-rw-r--r-- 1 willy willy 202871 Apr 8 20:54 parisc-2.5.diff
although most of that is:
-rw-r--r-- 1 willy willy 170361 Mar 18 18:46 parisc-hil.diff
$ zcat ../ftp/cvs/patch-2.4.20-pa32.diff.gz |wc
91100 503494 3691507
that's not the full story since a large chunk of that's been merged into
2.4.21-pre, but i have no idea how much would be remaining.
if anyone had the time, we could track 2.4.21-pre more closely. but it's
just not worth it.
--
"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
next prev parent reply other threads:[~2003-04-10 11:19 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
2003-04-10 11:19 ` Matthew Wilcox [this message]
-- 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=20030410111926.GR23430@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=grundler@parisc-linux.org \
--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