From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Keitaro Yosimura <ramsy@linux.or.jp>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Configure.help i18n system
Date: Thu, 7 Jun 2001 15:44:57 -0600 [thread overview]
Message-ID: <200106072144.f57LivR32508@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.21.0106071351300.6604-100000@penguin.transmeta.com>
In-Reply-To: <20010607165007.A299.RAMSY@linux.or.jp> <Pine.LNX.4.21.0106071351300.6604-100000@penguin.transmeta.com>
Linus Torvalds writes:
> Configure.help certainly isn't all that kernel version dependent,
> and could successfully be maintained completely outside the kernel,
> I suspect.
It might not change much, but it can from time to time. The meaning of
a particular option can evolve over time. I wouldn't want to see
options have sections like "for kernel x.y.z the behaviour is this,
but for kernel a.b.c the behaviour is thus". It's just clutter.
Another issue is ease of use. I just want to be able to download a
single tarball, and then be able to go offline and configure, compile,
read docs and so on. One example of this is when setting up a new
box. Another is when I'm on the road, dial in and download a new patch
and then hop on a plane and start playing with it.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2001-06-07 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010607165007.A299.RAMSY@linux.or.jp>
2001-06-07 21:01 ` Linus Torvalds
2001-06-07 21:23 ` Horst von Brand
2001-06-07 21:44 ` Richard Gooch [this message]
2001-06-08 1:21 ` GOTO Masanori
2001-06-07 21:46 Andries.Brouwer
2001-06-08 9:12 ` Francois Romieu
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=200106072144.f57LivR32508@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ramsy@linux.or.jp \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®