From: Nick Warne <nick@linicks.net>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question on Space.c
Date: Mon, 29 May 2006 19:11:25 +0100 [thread overview]
Message-ID: <200605291911.25836.nick@linicks.net> (raw)
In-Reply-To: <9a8748490605291105v42e66303pbb45fdccec3a13e4@mail.gmail.com>
On Monday 29 May 2006 19:05, Jesper Juhl wrote:
> On 29/05/06, Nick Warne <nick@linicks.net> wrote:
> > I saw Space.o being build, and seeing as it is Capitalised thought I
> > would see why, and maybe a patch to make it all lower case.
>
> [snip]
>
> > I have looked though docs and googled as to why this One File Is Like
> > This to no avail? Convention?
>
> The normal convention is for filenames to be all lowercase except for
> some special ones like "Makefile", "Kconfig", "README" etc (although
> there are a few exceptions,for source files, like
> drivers/scsi/NCR5380.c, include/asm-m68knommu/MC68328.h,
> drivers/block/DAC960.c and others).
> To find some more, try this in the kernel source dir : find ./ -name
> "[A-Z]*"
>
> It would make sense to me personally to rename this one, but it's not
> my call and besides it'll open a whole can of worms about whether or
> not to rename the other ones...
Well, I don't think so. Apart from the really conventional file names
(Makefile et al), the others you mentioned are abbreviations*, so it is
obvious. Now Ncr5380.c would be a different kettle of fish...
Nick
* abbreviation: a long word used to describe a short word used in place of a
long word.
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
next prev parent reply other threads:[~2006-05-29 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 17:49 Question on Space.c Nick Warne
2006-05-29 18:05 ` Jesper Juhl
2006-05-29 18:11 ` Nick Warne [this message]
2006-05-29 19:03 ` Al Viro
2006-05-29 18:06 ` Brian F. G. Bidulock
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=200605291911.25836.nick@linicks.net \
--to=nick@linicks.net \
--cc=jesper.juhl@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox