mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc2 crashes
Date: Tue, 27 Jul 2004 14:36:23 -0400	[thread overview]
Message-ID: <200407271436.23097.gene.heskett@verizon.net> (raw)
In-Reply-To: <20040727105039.052352d8.rddunlap@osdl.org>

On Tuesday 27 July 2004 13:50, Randy.Dunlap wrote:
>On Tue, 27 Jul 2004 14:02:59 -0400 Gene Heskett wrote:
>| On Tuesday 27 July 2004 13:32, Randy.Dunlap wrote:
>| [...]
>|
>| Gene Heskett wrote:
>| >| I take it that I should apply these to a 2.6.7 tarballs tree in
>| >| this order:
>| >| 1. 2.6.8-rc1
>| >|
>| >>>>> 2.6.8-rc2 <<<<<
>|
>| 2.6.8-rc2?  These patches I got will need to be reverted then?
>
>Nope, my bad.  I didn't read $Subject... please continue....

Oh, mmm, well, for some unexplainable reason it did apply the patches 
on top of rc2 without any fussing, and it is building, ahh scuse me, 
is built.  This athlon 2800 is awesome, my makeit script runs in a 
bit over 6 minutes.  And unrelated of course, by now, the kde build 
has puked all over itself, it now doesn't like the glibc installed by 
FC2.  Go figure...

Anyway, now I'll go make it again using the 2.6.8-rc1 main patch & 
throw this one away.  Not that big a deal when there a 120Gb drive to 
play in.


>| >| 2. each of these 'rc2-bk' patches by the day and then run each
>| >| for a couple days, or should I start in the middle, say the 3rd
>| >| one and work forward or backwards from there depending on the
>| >| results?
>| >
>| >I'd suggest beginning with -bk3 and doing a binary search.
>|
>| Ok, as soon as the kde build exits (and it will, bet the whole
>| farm on it)  I'll give it a try.
>|
>| >| Your (and Viro's) call.  I'd imagine you would want to run this
>| >| to earth as quick as we can.
>| >|
>| >| Are these patches cumulative?  I presume they are as they grow
>| >| by the day.
>| >
>| >Sorry, I should have mentioned that.  Yes, they are cumulative.
>|
>| Well, it was a pretty obvious conclusion :)
>
>--
>~Randy

-- 
Cheers, Gene
There are 4 boxes to be used in defense of liberty. 
Soap, ballot, jury, and ammo.
Please use in that order, starting now.  -Ed Howdershelt, Author
Additions to this message made by Gene Heskett are Copyright 2004, 
Maurice E. Heskett, all rights reserved.

  reply	other threads:[~2004-07-27 18:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 16:33 Gene Heskett
2004-07-27 13:37 ` Denis Vlasenko
2004-07-27 14:29 ` viro
2004-07-27 17:02   ` Gene Heskett
2004-07-27 16:51     ` Randy.Dunlap
2004-07-27 17:43       ` Gene Heskett
2004-07-27 17:32         ` Randy.Dunlap
2004-07-27 18:02           ` Gene Heskett
2004-07-27 17:50             ` Randy.Dunlap
2004-07-27 18:36               ` Gene Heskett [this message]
2004-07-27 18:42               ` Gene Heskett
2004-07-27 19:23                 ` viro
2004-07-27 22:17                   ` Gene Heskett
2004-07-27 21:40             ` Matt Mackall
2004-07-27 22:21               ` Gene Heskett
2004-07-27 17:15   ` Gene Heskett
2004-07-27 19:26     ` viro
2004-07-27 22:24       ` Gene Heskett
2004-07-27 22:25       ` Gene Heskett
2004-07-28 11:20       ` Gene Heskett
2004-07-28 11:38         ` Andy Whitcroft
2004-07-28 12:52           ` Gene Heskett
2004-07-27 17:31   ` Gene Heskett
2004-07-28 23:26     ` Gene Heskett
2004-07-29 12:53       ` Gene Heskett

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=200407271436.23097.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --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

all inboxes | Powered by JetHome®