From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: benoit.boissinot@ens-lyon.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pekkas@netcore.fi,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] [RFC] [IPv6] spelling fix in /proc: /proc/sys/net/ipv6/conf/default/temp_prefered_lft
Date: Wed, 19 Mar 2008 16:17:30 -0700 [thread overview]
Message-ID: <47E19F0A.1010301@hp.com> (raw)
In-Reply-To: <20080319.135205.125229102.davem@davemloft.net>
David Miller wrote:
> From: Benoit Boissinot <benoit.boissinot@ens-lyon.org>
> Date: Wed, 19 Mar 2008 21:42:27 +0100
>
>
>>Is there a way to fix a bad spelling in /proc ?
>>
>>Here is a patch to fix all the spelling error (prefered -> preferred)
>>in the ipv6 code. I didn't change the /proc name but everything else is
>>changed.
>>Currently you can found both spelling in the ipv6 code.
>>Is it ok ?
>
>
> I think this doesn't add any value.
>
> If the procfs file name has to remain the same, which it does,
> changing variable and macro names to be different will only
> cause merge conflicts and pain yet have no redeeming value.
I've not split many hairs today so I'll ask - is there _no_ way to
migrate a name in /proc et al? While it may be minor to most, it would
seem that leaving spelling errors out where users see them doesn't
convey all that positive an image.
rick jones
next prev parent reply other threads:[~2008-03-19 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 20:42 [PATCH] [RFC] [IPv6] spelling fix in /proc: /proc/sys/net/ipv6/conf/default/temp_prefered_lft Benoit Boissinot
2008-03-19 20:52 ` David Miller
2008-03-19 23:17 ` Rick Jones [this message]
2008-03-19 23:53 ` David Miller
2008-03-20 1:25 ` Joe Perches
2008-03-20 1:56 ` David Miller
2008-03-20 9:00 ` Benoit Boissinot
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=47E19F0A.1010301@hp.com \
--to=rick.jones2@hp.com \
--cc=benoit.boissinot@ens-lyon.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).