public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.21: kbuild changes broke filenames with commas
Date: Tue, 11 Jun 2002 14:01:22 +0100	[thread overview]
Message-ID: <20020611140122.B3665@flint.arm.linux.org.uk> (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:
> Well the question is then how will things look without commas? I suppose 
> if we have very complex things and prevent using commas whereas I don't 
> assert that we do for text but this is just a bloat example it's good to 
> have things like commas allowed even though we are in case we won't allow 
> them there talking about file names.
> 
> 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?

You've *completely* missed the point.

The gcc argument >>> -Wp,-MD,foo,bar.c <<< is the problem.  If anything
should be fixed, its that silly gcc syntax.  kbuild should not work
around the inability of gcc to accept filenames with commas in.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-06-11 13:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09 16:58 2.5.21: kbuild changes broke filenames with commas 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 [this message]
2002-06-12 14:36           ` Ingo Oeser
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
  -- strict thread matches above, loose matches on Subject: below --
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=20020611140122.B3665@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=kaos@ocs.com.au \
    --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