From: Luben Tuikov <luben@splentec.com>
To: Andrew Morton <akpm@digeo.com>
Cc: hch@infradead.org, patmans@us.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [RFC][PATCH] scsi-misc-2.5 software enqueue when can_queue reached
Date: Mon, 03 Mar 2003 23:49:59 -0500 [thread overview]
Message-ID: <3E643077.100@splentec.com> (raw)
In-Reply-To: <20030303171116.0ca432a0.akpm@digeo.com>
Andrew Morton wrote:
> Luben Tuikov <luben@splentec.com> wrote:
>
>>>Linux codingstyle sais the && should be before the line break.
>>
>>Actually there's a point to this.
>>
>
>
> Sorry, but tough luck.
What do you mean?
> The advantages of everyone using the same coding style outweigh the arguable
> marginal benefits of introducing local inconsistencies.
I wasn't ``introducing local inconsistencies'', I was merely stating
a few facts. And if you had quoted my whole letter you'd see that
I did not express personal opinion on the subject -- we already
have coding police. :-)
> I was a braces-on-a-new-line guy for nearly 20 years, but I knuckled under
> and learnt to use Linus-style for this reason. I'm sure others can manage
> this.
After Pascal, I learned C from K&R1 over a decade ago.
In general I don't really care *that* much about the style
as long as it is K&R1 and the tabs are 8 spaces. I care more
about the logistics in the code.
--
Luben
next prev parent reply other threads:[~2003-03-04 4:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 19:19 [RFC][PATCH] scsi-misc-2.5 software enqueue when can_queue reached Patrick Mansfield
2003-03-02 8:57 ` Christoph Hellwig
2003-03-02 18:15 ` Patrick Mansfield
2003-03-03 15:52 ` Randy.Dunlap
2003-03-03 18:17 ` Luben Tuikov
2003-03-04 1:11 ` Andrew Morton
2003-03-04 4:49 ` Luben Tuikov [this message]
2003-03-02 20:57 ` Luben Tuikov
2003-03-02 21:08 ` Luben Tuikov
2003-03-03 20:52 ` Patrick Mansfield
2003-03-03 22:40 ` Luben Tuikov
2003-03-03 23:41 ` Patrick Mansfield
2003-03-04 5:48 ` Luben Tuikov
2003-03-05 3:02 ` James Bottomley
2003-03-05 18:43 ` Patrick Mansfield
2003-03-06 15:57 ` James Bottomley
2003-03-06 17:41 ` Patrick Mansfield
2003-03-06 18:04 ` James Bottomley
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=3E643077.100@splentec.com \
--to=luben@splentec.com \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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