From: Jim Freeman <jfree@sovereign.org>
To: "Eric S. Raymond" <esr@thyrsus.com>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Re: Remaining undocumented Configure.help symbols
Date: Fri, 1 Jun 2001 07:54:27 -0600 [thread overview]
Message-ID: <20010601075427.A23321@sovereign.org> (raw)
In-Reply-To: <20010529145940.A11498@thyrsus.com> <20010530185542.R14293@corellia.laforge.distro.conectiva> <20010530182012.D1305@thyrsus.com> <20010531144328.A16811@sovereign.org> <20010531191055.A13056@thyrsus.com>
In-Reply-To: <20010531191055.A13056@thyrsus.com>
On Thu, May 31, 2001 at 07:10:55PM -0400, Eric S. Raymond wrote:
> Jim Freeman <jfree@sovereign.org>:
> > The verbiage in these entries seems 'make config' / text-interaction
> > -centric. Granted, that's likely the context most kernel builders will
> > use, but it would seem fair to at least consider a broader audience
> > who may be using more gui-ish tools wrapped around extant content.
>
> This is a general problem with almost all the existing entries, and
> will have to await a future editing pass for solution. For now I think
> it's more important to have consistent cues that users can recognize,
> even if they're not literally appropriate.
Agreed - in the meantime, just wanted to have the issue acknowledged
and put on the roadmap.
prev parent reply other threads:[~2001-06-01 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 18:59 Remaining undocumented Configure.help symbols Eric S. Raymond
2001-05-30 21:55 ` Harald Welte
2001-05-30 22:20 ` Eric S. Raymond
2001-05-30 22:50 ` Jim Treadway
2001-05-31 20:43 ` Jim Freeman
2001-05-31 23:10 ` [kbuild-devel] " Eric S. Raymond
2001-06-01 13:54 ` Jim Freeman [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=20010601075427.A23321@sovereign.org \
--to=jfree@sovereign.org \
--cc=esr@thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--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.