linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: linux kernel conf 0.7
Date: Sun, 29 Sep 2002 02:00:50 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0209290133380.338-100000@serv> (raw)
In-Reply-To: <20020929004821.A11497@mars.ravnborg.org>

Hi,

On Sun, 29 Sep 2002, Sam Ravnborg wrote:

> 1) Old tools zapped <file:> tags around filenames.

Ok.

> > An issue (which was also mentioned by Jeff Garzik) is the help text
> > format. Jeff likes to have an endhelp, where I think it's redundant.
> 2) The current way forces the layout of the help text. I would prefer a way
> that allowed the tools to use the space available instead.
> Then a "." followed by newline could be interpreted as "forced-new-line"
> or similar.
> If endhelp is needed for that I vote for this as well.

The problem is that the Config.help format has almost no restrictions, so
somehow I have to avoid messing up the content (at least for the
majority of options), so far I tried to avoid to reformat all the help
text.
Another possibility might to use html tags.

> 3) The syntax seems to be:
> config SYMBOL
> 	type-of-symbol optional-text
> I would like "optional-text" to become mandatory. Then you could bail out
> with an error when it does not exist.

Why should it be an error? Symbols without a text are used for derived
symbols.

> 4) Did not find the documentation you mentioned, but on the other hand I
> applied only the 2.3.39 diff.

It's on the web. :)

> 5) Show All intuitively is a shortcut for selecting all the three
> possibilities {NAME, RANGE, DATA}, but is about showing all symbols.
> 6) The ARCH specific options does not fit well into the tree.
> GENERIC_ISA_DMA in top of tree, X86_SMP in bottom of tree.
> Visible only with SHOW ALL enabled.

"Show All" is mostly only a debug option, so what you see here isn't
important to the normal user.

> 7) I can step down in the tree but I need to select each sibling in the tree
> induvidially. I expected to be able to select Cirrus logic under ALSA, and
> let the selection boil up to the top.

This is a planned feature, first I want to have a replacement for the old
tools, new features come later.
I suppose you use QT2 and "Show All" was active? Then it can be a bit
confusing since the usually not visible items are not specially marked.

> 8) File|Save followed by File|Quit. Still it ask if I want to save, even
> no changes made inbetween.

Simple to do.

> 9) Renames a file in a source statement:
> [sam@mars lkc-2.5.39]$ make xconfig
> make[1]: `qconf' is up to date.
> ./scripts/lkc/qconf arch/i386/Build.conf
> can't find file ssound/arm/Build.conf
> make: *** [xconfig] Error 1
>
> Error shall tell where the file is sourced. [.../Build.conf:27]
>
> 10) Deleted endmenu tag in sound/Build.conf:
> [sam@mars lkc-2.5.39]$ make xconfig
> make[1]: `qconf' is up to date.
> ./scripts/lkc/qconf arch/i386/Build.conf
> <none>:0:parse error, unexpected $
> make: *** [xconfig] Error 1
>
> Some errorhandling needs to be improved a little.

I know and it slowly moves to the top of the TODO list. :)

bye, Roman


      reply	other threads:[~2002-09-28 23:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28 14:25 linux kernel conf 0.7 Roman Zippel
2002-09-28 14:42 ` Tomas Szepe
2002-09-28 15:15   ` Roman Zippel
2002-09-28 15:41   ` Roman Zippel
2002-09-28 22:48 ` Sam Ravnborg
2002-09-29  0:00   ` Roman Zippel [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=Pine.LNX.4.44.0209290133380.338-100000@serv \
    --to=zippel@linux-m68k.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).