All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wayne.Brown@altec.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: esr@thyrsus.com, alan@lxorguk.ukuu.org.uk (Alan Cox),
	kaos@ocs.com.au (Keith Owens),
	linux-kernel@vger.kernel.org (CML2),
	kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Why recovering from broken configs is too hard
Date: Thu, 3 May 2001 14:30:14 -0500	[thread overview]
Message-ID: <86256A41.006B2177.00@smtpnotes.altec.com> (raw)



Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

>Its worked well enough for the past five years. On odd occasions you do find
>you've inadventantly unconfigured something but normally the conflict vanishes
>with almost no ripples.

>I'm quite happy for oldconfig to continue to do what it did before. I'm quite
>happy to accept its mathematically imperfect, because it hasnt gone far wrong
>yet

Here's a real-life example of how well it works.  I tend to bounce back and
forth between Linus' -pre patches and your -ac patches.  For instance, when
2.4.4-ac4 came out, I was running 2.4.5-pre1.  Here's what I did:

zcat patch-2.4.5-pre1.gz | patch -p1 -s -E -R
zcat patch-2.4.4-ac4.gz | patch -p1 -s -E
mv .config ..
make mrproper
mv ../.config .
make oldconfig
make dep && make bzlilo modules modules_install

I apply nearly every patch set that comes along from you or Linus, and this is
the way I usually do it.  Every once in a while, I run through all the options
in menuconfig just to make certain nothing has gotten hosed up.  Only once can I
remember needing to change an option that had been set incorrectly by oldconfig.

Wayne



             reply	other threads:[~2001-05-03 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-03 19:30 Wayne.Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-03  7:47 Why recovering from broken configs is too hard Eric S. Raymond
2001-05-03  8:42 ` [kbuild-devel] " Greg Banks
2001-05-03  8:52   ` Eric S. Raymond
2001-05-03 10:15 ` Keith Owens
2001-05-03 16:59   ` Eric S. Raymond
2001-05-03 17:48     ` Alan Cox
2001-05-03 18:30       ` Eric S. Raymond
2001-05-03 18:41         ` Alan Cox
2001-05-03 22:58     ` Keith Owens

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=86256A41.006B2177.00@smtpnotes.altec.com \
    --to=wayne.brown@altec.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=esr@thyrsus.com \
    --cc=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.