From: Alexander Winston <alexander.winston@comcast.net>
To: Jasper Spaans <jasper@vs19.net>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Change all occurrences of 'flavour' to 'flavor'
Date: Fri, 08 Aug 2003 03:07:32 -0400 [thread overview]
Message-ID: <3F334C34.90403@comcast.net> (raw)
In-Reply-To: <20030808065230.GA5996@spaans.vs19.net>
Jasper Spaans wrote:
>On Thu, Aug 07, 2003 at 09:42:37PM -0400, Zwane Mwaikambo wrote:
>
>
>
>>>It changes all occurrences of 'flavour' to 'flavor' in the complete tree;
>>>I've just comiled all affected files (that is, the config resulting from
>>>make allyesconfig minus already broken stuff) succesfully on i386.
>>>
>>>
>>Arrrgh! You can't be serious!
>>
>>
>
>Yes, I am bloody serious; this patch might look purely cosmetic at first
>sight.. yet, there's a technical reason for at least one part of it. Grep
>and see the horror:
>
>$ egrep -ni 'flavou?r' fs/nfs/inode.c
>[snip]
>1357: rpc_authflavor_t authflavour;
>[snip]
>
>VrGr,
>
I think another important issue is consistency. We should choose a
style, and then stick with it.
next prev parent reply other threads:[~2003-08-08 7:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 18:00 [PATCH] Change all occurrences of 'flavour' to 'flavor' Jasper Spaans
2003-08-07 22:37 ` Alan Cox
2003-08-08 0:04 ` Martin J. Bligh
2003-08-08 16:54 ` Steven Cole
2003-08-08 5:46 ` [PATCH] Change all occurrences of 'flavour' to 'flavor', torvalds@osdl.org Jasper Spaans
[not found] ` <200308080153.22495.jcwren@jcwren.com>
2003-08-08 5:58 ` [ot] Re: [PATCH] Change all occurrences of 'flavour' to 'flavor' Jasper Spaans
2003-08-08 7:13 ` Jens Axboe
2003-08-08 1:42 ` Zwane Mwaikambo
2003-08-08 6:52 ` Jasper Spaans
2003-08-08 6:57 ` Zwane Mwaikambo
2003-08-08 7:15 ` Jens Axboe
2003-08-08 11:04 ` [OT] " Adrian Bunk
2003-08-08 16:58 ` Svein Ove Aas
2003-08-08 21:51 ` Ian Hastie
2003-08-08 7:33 ` Jasper Spaans
2003-08-08 7:40 ` Jens Axboe
2003-08-08 8:00 ` Jasper Spaans
2003-08-08 8:54 ` Jens Axboe
2003-08-08 7:45 ` Zwane Mwaikambo
2003-08-08 7:07 ` Alexander Winston [this message]
2003-08-08 7:31 ` Jasper Spaans
2003-08-08 7:11 ` Tomas Szepe
2003-08-08 15:18 ` Timothy Miller
2003-08-08 15:34 ` Richard B. Johnson
2003-08-08 15:48 ` Trond Myklebust
2003-08-08 16:42 ` Gene Heskett
2003-08-08 17:03 ` Jasper Spaans
2003-08-08 17:34 ` Alan Cox
2003-08-08 18:02 ` Gene Heskett
2003-08-08 15:50 ` Jasper Spaans
2003-08-08 16:00 ` Richard B. Johnson
2003-08-08 17:18 ` Linus Torvalds
2003-08-08 17:33 ` Jasper Spaans
2003-08-09 0:24 ` Trond Myklebust
2003-08-09 0:41 ` Linus Torvalds
2003-08-09 0:45 ` Jasper Spaans
2003-08-09 19:56 ` [PATCH] Fix up fs/nfs/inode.c wrt flavo[u]r Jasper Spaans
2003-08-09 19:51 ` Zwane Mwaikambo
2003-08-09 21:41 ` [PATCH] Fix up fs/nfs/inode.c wrt flavo[u]r, try 2 Jasper Spaans
2003-08-09 1:04 ` [PATCH] Change all occurrences of 'flavour' to 'flavor' Trond Myklebust
2003-08-09 1:17 ` Ian Hastie
2003-08-09 7:23 ` jw schultz
2003-08-07 20:40 Andries.Brouwer
2003-08-08 8:25 Andries.Brouwer
2004-01-13 13:35 Andries.Brouwer
2004-01-13 13:42 Randal, Phil
2004-01-13 14:07 ` Måns Rullgård
2004-01-13 14:26 Nicholas Berry
2004-01-13 22:46 ` Peter Horton
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=3F334C34.90403@comcast.net \
--to=alexander.winston@comcast.net \
--cc=jasper@vs19.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zwane@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).