mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "mirabilos" <eccesys@topmail.de>
To: "Linux-Kernel ML" <linux-kernel@vger.kernel.org>
Subject: Re: spelling of disc (disk) in /devfs
Date: Fri, 2 Feb 2001 14:07:12 -0000	[thread overview]
Message-ID: <02b101c08d21$923c5ac0$0100a8c0@homeip.net> (raw)
In-Reply-To: <6lah7t4f685qo3igk679ocdo2obfhd9lvg@4ax.com> <20010201193255.A32191@thune.yy.com> <20010202115712.A31607@netppl.fi>

Oh you English people,

why do you do it so complicated?
We even don't need a kernel locale.

Take the nominations as they are, color/colour,
disk/disc/diskette/floppy, etc.

And if you write by yourself, do it as you spell it.
I'd even write it German if I wasn't used to speak
fully English whilst coding.

And dont bother about names:
 - Namen sind Schall und Rauch. Was zaehlt, ist das, was drin ist.
(for tho who can understand it. the others: sorry, it's a cite.)

Does it _actually_ make a prob to use disc in devfs instead
of the (correct) disk when changing it broke configuration?
We are _not_ M$, we (usually) _dont_ break old systems.
And __colour does only matter when you directly access it.

Really, it's inconsistent, but it happened - so...
You could consider changing it on a two-year solution:
create a hardlink /dev/disks <-> /dev/discs in the KERNEL(!!)
and remove /dev/discs in two years.
Meanwhile everyone reading docu will have upgraded ;-)
(ref. to the 4-week pause before ECN on vger.kernel.org)

-mirabilos

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12+(proprietary extensions) # Updated:20010129 nick=mirabilos
GO/S d@ s--: a--- C++ UL++++ P--- L++$(-^lang) E----(joe) W+(++) loc=.de
N? o K? w-(+$) O+>+++ M-- V- PS+++@ PE(--) Y+ PGP t+ 5? X+ R+ !tv(silly)
b++++* DI- D+ G(>++) e(^age) h! r(-) y--(!y+) /* lang=NASM;GW-BASIC;C */
------END GEEK CODE BLOCK------


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-02 14:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-01  0:19 Alan Chandler
2001-02-01  0:35 ` List User
2001-02-01 18:27   ` idalton
2001-02-01 19:07     ` alex
2001-02-01 19:08     ` Richard B. Johnson
2001-02-01 23:17       ` Harald Arnesen
2001-02-01  9:42 ` Jeremy M. Dolan
2001-01-31 23:00   ` Michael B. Trausch
2001-02-01 10:28   ` Peter Samuelson
2001-02-01 10:58     ` Alan Cox
2001-02-01 17:21       ` Peter Samuelson
2001-02-08 23:31     ` Thomas Dodd
2001-02-02  3:32 ` Mike Castle
2001-02-02  9:57   ` Pekka Pietikainen
2001-02-02 14:07     ` mirabilos [this message]
2001-02-02 15:47   ` David Woodhouse
2001-02-10  0:41 ` Dr. Kelsey Hudson
2001-02-10 23:17   ` Tony Hoyle
2001-02-10 23:51   ` Albert D. Cahalan
2001-02-11  0:22     ` Rik van Riel
2001-02-11  3:56     ` John Cavan
2001-02-01 23:04 Wayne.Brown
2001-02-01  0:32 ` Michael B. Trausch
2001-02-01 23:12 ` Mike Harrold
     [not found] <fa.gvan6kv.3664g1@ifi.uio.no>
     [not found] ` <fa.i0lgugv.dhmm08@ifi.uio.no>
2001-02-02 12:49   ` Tor Arntsen

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='02b101c08d21$923c5ac0$0100a8c0@homeip.net' \
    --to=eccesys@topmail.de \
    --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

all inboxes | Powered by JetHome®