public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@debian.org>
To: esr@thyrsus.com
Cc: reddog83 <reddog83@chartermi.net>, linux-kernel@vger.kernel.org
Subject: Re: CML2-2.0.4 is available
Date: Wed, 09 Jan 2002 09:44:18 +0100	[thread overview]
Message-ID: <3C3C02E2.4050008@debian.org> (raw)
In-Reply-To: <fa.ijumnqv.13juc98@ifi.uio.no> <fa.fvl9anv.u6q1pu@ifi.uio.no>

Eric S. Raymond wrote:
> 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.

Maybe better: use other keystrings. I.e. Control + key.
In this way is more difficult to press the wrong key sequence, but we
still have the full features in all modes.

	giacomo




       reply	other threads:[~2002-01-09  8:44 UTC|newest]

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