public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Crilly <jim@why.dont.jablowme.net>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.12
Date: Sat, 18 Jun 2005 15:20:33 -0400	[thread overview]
Message-ID: <20050618192033.GD24148@mail> (raw)
In-Reply-To: <200506182005.28254.nick@linicks.net>

On 06/18/05 08:05:28PM +0100, Nick Warne wrote:
> 
> Heh.  When I was sussing 2.6.12 stuff today, I really thought it was me 
> buggering up something.  So after reading a lot, I wondered (neurotically)  
> if I was doing anything wrong (after all this time, it's likely).
> 
> > make help reveals:
> 
>  randconfig      - New config with random answer to all options
> 
> So 'make randconfig' is the one to use!  What one earth is that for?

Weeding out dependencies that aren't in the make system yet.

> 
> Nick

Jim.

  reply	other threads:[~2005-06-18 19:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18 19:05 Linux 2.6.12 Nick Warne
2005-06-18 19:20 ` Jim Crilly [this message]
2005-06-18 19:33 ` Jesper Juhl
2005-06-19  1:39   ` aq
2005-06-19  1:48     ` David Lang
2005-06-19  2:36       ` randy_dunlap
2005-06-19  9:29         ` Ian Campbell
2005-06-19 15:00         ` aq
2005-06-20  9:36           ` Vincent Hanquez
2005-06-20 21:55     ` Matt Mackall
  -- strict thread matches above, loose matches on Subject: below --
2005-06-18  5:13 Linus Torvalds
2005-06-18  5:38 ` Keith Owens
2005-06-18  6:05   ` Linus Torvalds
2005-06-18  6:59     ` Willy Tarreau
2005-06-18 10:36       ` Jesper Juhl
2005-06-18 10:48         ` Alexey Dobriyan
2005-06-18 10:52           ` Jesper Juhl
2005-06-18 10:54           ` Brice Goglin
2005-06-18 17:42         ` Linus Torvalds
2005-06-18 18:26 ` Steven Rostedt

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=20050618192033.GD24148@mail \
    --to=jim@why.dont.jablowme.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    /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