All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Vesa-Matti J Kari <vmkari@cc.helsinki.fi>
Cc: Eric Paris <eparis@parisplace.org>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <jmorris@namei.org>,
	selinux@tycho.nsa.gov
Subject: Re: [patch] SELinux: trivial, unify iterator variable naming
Date: Mon, 21 Jul 2008 08:24:39 -0400	[thread overview]
Message-ID: <200807210824.40003.paul.moore@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64L.0807211104300.15292@ruuvi.it.helsinki.fi>

On Monday 21 July 2008 4:08:04 am Vesa-Matti J Kari wrote:
> Hello,
>
> On Sun, 20 Jul 2008, Paul Moore wrote:
> > Normally I like janitorial fixes such as whitespace cleanups,
> > spelling corrections, etc.  However, these three patches seem a bit
> > silly to me simply changing a variable name from "idx" to "i" and
> > not adding any real value to the code.  If it were up to me alone,
> > I would say "NO", but if everyone else agrees they are worthwhile I
> > won't to stand in the way.
>
> I understand, but my preference is that all code should always look
> as similar as possible style-wise. To my eyes, it is quite annoying
> to see, e.g. "iter" and "idx" used mixed in the same source file, and
> it distracts my code reading.

The kernel is a very large piece of code, which is developed and 
maintained by literally thousands of people.  While there are rules and 
guidelines to help maintain consistency there will _always_ be 
inconsistent style in the Linux Kernel.  Further, due to the extremely 
high rate of change in the kernel it is doubtful that you will be able 
to stylistically "fix" the entire kernel and maintain it (patch 
acceptance is another issue entirely).

I know it can be frustrating at times, but I would suggest that adapting 
yourself to read the Linux Kernel sources will be much more rewarding 
(both to yourself and to the community) than trying to adapt the kernel 
sources to you.

-- 
paul moore
linux @ hp

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2008-07-21 12:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20 21:46 [patch] SELinux: trivial, unify iterator variable naming Vesa-Matti J Kari
2008-07-21  1:25 ` Paul Moore
2008-07-21  8:08   ` Vesa-Matti J Kari
2008-07-21 12:24     ` Paul Moore [this message]
2008-07-21 13:08       ` Vesa-Matti J Kari
2008-07-21 13:38         ` Paul Moore
2008-07-22 18:21           ` Vesa-Matti J Kari
2008-07-23  3:10             ` Paul Moore
2008-07-30  2:47           ` Russell Coker
2008-07-30 15:22             ` Paul Moore
2008-07-30 16:04               ` Vesa-Matti J Kari

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=200807210824.40003.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=vmkari@cc.helsinki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.