public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: reddog83 <reddog83@chartermi.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CML2-2.0.4 is available
Date: Wed, 9 Jan 2002 01:33:37 -0500	[thread overview]
Message-ID: <20020109013337.A11149@thyrsus.com> (raw)
In-Reply-To: <auto-000047128443@front2.chartermi.net>
In-Reply-To: <auto-000047128443@front2.chartermi.net>; from reddog83@chartermi.net on Wed, Jan 09, 2002 at 01:47:39AM -0500

reddog83 <reddog83@chartermi.net>:
> There is one thing though when a newie come's over say to Linux Kernel 
> 2.6/3.0 and is starting out using the new CML2 system he could acidentialy 
> hit the wroung key and all the other option's for the other Linux Kernel 
> port's will show up and he could click on one of the and try to make a kernel 
> that is for a x86 and he could be clicking in the IA64 port menu on acident.
> Do you see what I'm saying?
> I have done it before and I downloaded CML2 2.0.3 and I did it again

Yes.  This will happen if you happen if you toggle the suppression flag.
I'm considering disabling that unless you're in expert mode.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

Love your country, but never trust its government.
	-- Robert A. Heinlein.

  reply	other threads:[~2002-01-09  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09  6:47 CML2-2.0.4 is available reddog83
2002-01-09  6:33 ` Eric S. Raymond [this message]
     [not found] <fa.ijumnqv.13juc98@ifi.uio.no>
     [not found] ` <fa.fvl9anv.u6q1pu@ifi.uio.no>
2002-01-09  8:44   ` Giacomo Catenazzi
2002-01-09 17:13     ` Eric S. Raymond
2002-01-10  9:17       ` Giacomo Catenazzi
  -- strict thread matches above, loose matches on Subject: below --
2002-01-09  7:13 reddog83
2002-01-09  5:57 Eric S. Raymond

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=20020109013337.A11149@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reddog83@chartermi.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