All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Brad Hards <bhards@bigpond.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC patch] Config re-org for storage devices
Date: Mon, 08 Jul 2002 14:40:03 +0200	[thread overview]
Message-ID: <3D298823.6040503@evision-ventures.com> (raw)
In-Reply-To: 200207082219.08470.bhards@bigpond.net.au

Użytkownik Brad Hards napisał:
> I'm looking at usability cleanups on the configuration files ([Cc]onfig.in).
> 
> The main concepts are to keep related menu entries together without excessive
> resort to 'misc" and "general", and to keep xconfig and menuconfig entries to
> about a screenful. Those two concepts are sometimes contradictory....
> 
> The current focus is on the various mass storage drivers. I plan to group them
> all under a single menu entry (done for i386, easily extensible to other arch,
> except for sparc of course). The main changes are pulling the parallel port
> IDE stuff out of the rest of block to a separate menu item, pulling QIC02 and
> ftape out of the rest of char(!) and some (fairly dubious) changes to the way
> IDE configuration works.
> 
> Find below a draft patch for comment. Even fflames would be good - at least it
> would show people read this stuff.

Looked thorugh it. No need for flaming found. The IDE changes are
fine. However a "subsystem by subsystem" patch approach would
help, since I could for example pull the stuff I care about out
and test it without regression concerns for the other things.


      reply	other threads:[~2002-07-08 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 12:19 [RFC patch] Config re-org for storage devices Brad Hards
2002-07-08 12:40 ` Martin Dalecki [this message]

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=3D298823.6040503@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=bhards@bigpond.net.au \
    --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.