From: Rusty Russell <rusty@rustcorp.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
geert@linux-m68k.org, linux-scsi@vger.kernel.org,
Greg Banks <gnb@alphalink.com.au>
Subject: Re: [TRIVIAL] PATCH 2.5: kconfig sychronise banners (2_16)
Date: Thu, 08 Aug 2002 12:10:18 +1000 [thread overview]
Message-ID: <20020808032826.BA88E4A84@lists.samba.org> (raw)
In-Reply-To: Your message of "07 Aug 2002 12:35:41 +0100." <1028720141.18478.244.camel@irongate.swansea.linux.org.uk>
In message <1028720141.18478.244.camel@irongate.swansea.linux.org.uk> you write
:
> On Wed, 2002-08-07 at 05:06, Rusty Trivial Russell wrote:
> > From: Greg Banks <gnb@alphalink.com.au>
> >
> > (Included in 2.5)
> > G'day,
> >
> >
> > 2/5 definitions of CONFIG_BLK_DEV_SR have trivially different banners.
>
> 2.5 is wrong, 2.4 is right. At least according to Philips who invented
> the things. Please submit the reverse diff to 2.5 8)
<SIGH>
CDROM seems pretty prevelent in the kernel over CD-ROM.
Unification of the banners is a trivial first step to furthur removal
of things that are gratuitously arch-dependent: this wasn't primarily
a spelling fix.
s/CDROM/CD-ROM/ would probably come under the new "too trivial for
trivial patch monkey rule" in normal circumstances 8)
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-08-08 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 4:06 [TRIVIAL] PATCH 2.5: kconfig sychronise banners (2_16) Rusty Trivial Russell
2002-08-07 11:35 ` Alan Cox
2002-08-08 2:10 ` Rusty Russell [this message]
2002-08-09 13:29 ` Greg Banks
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=20020808032826.BA88E4A84@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=gnb@alphalink.com.au \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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