From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Thunder from the hill <thunder@ngforever.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.21: kbuild changes broke filenames with commas
Date: Wed, 12 Jun 2002 16:36:35 +0200 [thread overview]
Message-ID: <20020612163635.D22429@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20020611122144.A3665@flint.arm.linux.org.uk> <Pine.LNX.4.44.0206110611590.24261-100000@hawkeye.luckynet.adm>
On Tue, Jun 11, 2002 at 06:16:10AM -0600, Thunder from the hill wrote:
> If we allow commas all over the filesystem and likewise say that there is
> nothing to mention about it why should we refuse them for kbuild
> especially since there is a parallel system which allows commas?
Aehm, if you argument with what we allow in the filesystem, then
I could argue, that everything except '\0' and '/' is allowed
to build paths.
Interesting is what the C-Standard says about naming conventions
for files.
The rest is merely taste and limitations of the build system.
I like ',' as much as ' ' and quotes in file names. But sh*t
happens and we usally have to cope with it :-/
Regards
Ingo Oeser
--
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth
next prev parent reply other threads:[~2002-06-12 15:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 16:58 Russell King
2002-06-09 17:11 ` Upper limits to number of processes / threads in Linux / ia32?? M. Edward (Ed) Borasky
2002-06-09 18:02 ` 2.5.21: kbuild changes broke filenames with commas Kai Germaschewski
2002-06-09 18:34 ` Tom Rini
2002-06-10 23:02 ` Keith Owens
2002-06-11 7:39 ` Russell King
2002-06-11 11:11 ` Thunder from the hill
2002-06-11 11:21 ` Russell King
2002-06-11 12:16 ` Thunder from the hill
2002-06-11 13:01 ` Russell King
2002-06-12 14:36 ` Ingo Oeser [this message]
2002-06-12 18:10 ` Thunder from the hill
2002-06-13 20:12 ` Thunder from the hill
2002-06-11 16:08 ` Daniel Phillips
2002-06-11 16:14 ` Alexander Viro
2002-06-11 16:22 ` Daniel Phillips
2002-06-11 16:31 ` Russell King
2002-06-11 16:36 ` Daniel Phillips
2002-06-11 23:55 Keith Owens
2002-06-12 0:27 ` Kai Germaschewski
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=20020612163635.D22429@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
/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®