From: Matthias Schniedermeyer <ms@citd.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christoph Hellwig <hch@caldera.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.1-ac5
Date: Wed, 7 Feb 2001 21:54:23 +0100 [thread overview]
Message-ID: <20010207215423.A17404@citd.de> (raw)
In-Reply-To: <200102072030.VAA06500@ns.caldera.de> <E14QbMw-0001JD-00@the-village.bc.nu>
In-Reply-To: <E14QbMw-0001JD-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 07, 2001 at 08:39:12PM +0000
> > now that -ac grows that huge, could you put out incremental patches?
>
> Takes me too much time. But if anyone else wants to, go ahead
This is what i use to diff 2 different kernels
- snip -
diffkernel)
mount none /d/kernel -t ramfs
cd /d/kernel
tar -zxf $1
cp -a linux linuxa
cd /d/kernel/linuxa
zcat $2 | patch -p1 -E -s
cd /d/kernel/linux
zcat $3 | patch -p1 -E -s
cd /d/kernel
diff -Nur linuxa linux
cd
umount /d/kernel
- snip -
This takes about 8 seconds (for 2.4 kernels) on my Dual PIII-933, 1Gig-RAM
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-07 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 20:10 Linux 2.4.1-ac5 Alan Cox
2001-02-07 20:30 ` Christoph Hellwig
2001-02-07 20:39 ` Alan Cox
2001-02-07 20:54 ` Matthias Schniedermeyer [this message]
2001-02-07 21:03 ` Adrian Bunk
2001-02-07 22:13 ` [bug] aic7xxx panic " Tigran Aivazian
2001-02-07 23:29 ` J . A . Magallon
2001-02-08 0:02 ` Doug Ledford
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=20010207215423.A17404@citd.de \
--to=ms@citd.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.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