public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: sam@ravnborg.org (Sam Ravnborg)
Cc: sampson@attglobal.net, linux-kernel@vger.kernel.org,
	mec@shout.net, zippel@linux-m68k.org
Subject: Re: First Bug Found : RE: How to help new comers trying the v2.5x series kernels.
Date: Sat, 21 Dec 2002 22:18:35 +0000 (GMT)	[thread overview]
Message-ID: <200212212218.gBLMIate002167@darkstar.example.net> (raw)
In-Reply-To: <20021221215250.GA1905@mars.ravnborg.org> from "Sam Ravnborg" at Dec 21, 2002 10:52:50 PM

> > The MAINTAINERS file tells you who to contact, (as well as this list):
> > 
> > CONFIGURE, MENUCONFIG, XCONFIG
> > P:      Michael Elizabeth Chastain
> 
> Despite the MAINTANERS file, roman Zippel is the right person to contact.
> roman ripped out three different shell ased parsers and replaced them
> with a single parser written in yacc and c.
> During this process 2make menuconfig" functionality was altered.

Whoops, sorry, I should have realised, especially as I was discussing
that menuconfig problem a couple of weeks ago :-)

John.

  reply	other threads:[~2002-12-21 22:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21 17:57 How to help new comers trying the v2.5x series kernels Sampson Fung
2002-12-21 18:16 ` John Bradford
2002-12-21 18:30   ` Sampson Fung
2002-12-21 19:05     ` Sam Ravnborg
2002-12-21 20:35       ` First Bug Found : " Sampson Fung
2002-12-21 21:23         ` John Bradford
2002-12-21 21:52           ` Sam Ravnborg
2002-12-21 22:18             ` John Bradford [this message]
2002-12-24 13:33       ` Additional Bug Found--RE: " Sampson Fung
2002-12-21 19:15     ` John Bradford
  -- strict thread matches above, loose matches on Subject: below --
2002-12-22  5:07 First Bug Found : " Michael Elizabeth Chastain

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=200212212218.gBLMIate002167@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mec@shout.net \
    --cc=sam@ravnborg.org \
    --cc=sampson@attglobal.net \
    --cc=zippel@linux-m68k.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