From: David Weinehall <tao@acc.umu.se>
To: Wayne.Brown@altec.com
Cc: Nick Holloway <Nick.Holloway@pyrites.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Change of policy for future 2.2 driver submissions
Date: Mon, 8 Jan 2001 12:07:08 +0100 [thread overview]
Message-ID: <20010108120708.C4991@khan.acc.umu.se> (raw)
In-Reply-To: <862569CE.001C2A47.00@smtpnotes.altec.com>
In-Reply-To: <862569CE.001C2A47.00@smtpnotes.altec.com>; from Wayne.Brown@altec.com on Sun, Jan 07, 2001 at 10:52:48PM -0600
On Sun, Jan 07, 2001 at 10:52:48PM -0600, Wayne.Brown@altec.com wrote:
>
>
> Actually, I have another reason for using patch-kernel, besides being
> inexperienced or lazy: being weird. :-) For some reason, I have an
> aversion to downloading complete kernels, and just grab the patches.
> That's usually OK, because I apply each patch one at a time, within a
> few hours after it comes out. But once in a while I mess up and have
> to start over -- like a few days ago, when I forgot to reverse
> prelease-diff before trying to apply 2.4.0-prelease-to-final. I got
You know, there are reasons why patch has an option called --dry-run...
bzcat patch-2.4.0.bz2 | patch -p1 --dry-run
[and if everything goes well]
bzcat patch-2.4.0.bz2 | patch -p1
[will be relatively painless, as the files will be cached by now...]
Is the way I usually apply patches.
Oh, and after applying a patch I always rename the directory to match
the version of the patch. This way I always know if I have to unapply
any pre-patches/test-patches/whatever.
> the kernel source tree hosed up so badly that I decided to blow it all
> away and get a clean copy. Instead of doing the sensible thing --
> getting a fresh copy of 2.4.0 -- I untarred 2.2.16 (the most recent
> tarball I had), reverse-patched it down to 2.2.8, applied
> patch-2.2.8-to-2.3.0, used patch-kernel to get up to 2.3.51, then
> applied the patches for 2.3.99-pre1 through -pre9 and 2.4.0-test1
> through -test12, and finally 2.4.0-prelease and
> 2.4.0-prerelease-to-final. Sure, it's insane, but it's not as tedious
Yup, you're one sick little puppy. Way cool :^)
> as it sounds, since I put together a script to do all this (and it
> doesn't take all that long on my Pentium III, especially if I shut
> down X first). Anyway, I've kind of been hoping that now that 2.4.0
> is out, maybe future patches will go back to the x.y.z format so I
> could just let patch-kernel do everything.
/David Weinehall
_ _
// David Weinehall <tao@acc.umu.se> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky //
\> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
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-01-08 11:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 4:52 Wayne.Brown
2001-01-08 11:07 ` David Weinehall [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:36 Wayne.Brown
2001-01-05 20:33 Wayne.Brown
2001-01-06 10:15 ` Nick Holloway
2001-01-05 17:32 Wayne.Brown
2001-01-05 18:50 ` Matthew D. Pitts
2001-01-05 17:11 Wayne.Brown
2001-01-05 17:15 ` Alan Cox
2001-01-05 17:23 ` Christoph.Hellwig.
[not found] ` <hchÀcaldera.de>
2001-01-05 17:31 ` Alan Cox
2001-01-05 3:50 Michael D. Crawford
2001-01-05 8:29 ` Miles Lane
2001-01-05 17:31 ` Linus Torvalds
2001-01-09 14:49 ` Hubert Mantel
2001-01-09 14:54 ` Alan Cox
2001-01-09 23:49 ` Jakob Østergaard
2001-01-10 0:02 ` Linus Torvalds
2001-01-10 0:33 ` Ingo Molnar
2001-01-10 1:03 ` Andrea Arcangeli
2001-01-10 1:17 ` Ingo Molnar
2001-01-10 1:40 ` Andrea Arcangeli
2001-01-05 2:41 Alan Cox
2001-01-05 3:27 ` Nicholas Knight
2001-01-05 4:23 ` Mark Hahn
2001-01-05 12:52 ` Daniel Phillips
2001-01-05 6:38 ` Tim Riker
2001-01-05 6:57 ` Andre Tomt
2001-01-05 7:30 ` Gerhard Mack
2001-01-05 11:46 ` Rik van Riel
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=20010108120708.C4991@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=Nick.Holloway@pyrites.org.uk \
--cc=Wayne.Brown@altec.com \
--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
Powered by JetHome