From: "Nick Warne" <nick@linicks.net>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: "Chris Boot" <bootc@bootc.net>,
"Matheus Izvekov" <mizvekov@gmail.com>,
"Pavel Machek" <pavel@ucw.cz>,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: SubmittingPatches typo
Date: Mon, 20 Mar 2006 22:02:52 +0000 [thread overview]
Message-ID: <7c3341450603201402k54b0cd6cy@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603202216390.15483@yvahk01.tjqt.qr>
Believe me, English Grammar is harder than trying to understand kernel code.
I was taught that 'ownership' and 'owner' decide, depending on the tense.
Fred's code (it's his - 'Fred has ['s] code')). - Here also "it's" is
short for "it is" (sucking eggs).
Freds' code. You are talking third party about Freds' (or should that
be Fred's?) code that he owns.
Names that end in 's' may not be plural... the Smiths family? Or the
Smiths' Family? What happens if you are talking about 10
Smiths'/Smith's families? Smiths Families?
So, I think:
Torvald's code == Torvalds has code == Torvald's ['s == has]
Reference Torvalds' code = Torvalds[es]' code [owner]
This debate has been on this board been a few times... and with all
the English masters in there, it is still a little bit unresolved.
http://www.b2g2.com/boards/board.cgi?user=dharrison
Stick to coding kernels guys, it's easier.
The fix?
+Here is the mail Linus Torvalds sent on the canonical patch format:
Nick
next prev parent reply other threads:[~2006-03-20 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 12:50 SubmittingPatches typo Pavel Machek
2006-03-20 19:57 ` Jan Engelhardt
2006-03-20 20:47 ` Matheus Izvekov
2006-03-20 20:53 ` Chris Boot
2006-03-20 20:55 ` Pavel Machek
2006-03-20 20:56 ` Jan Engelhardt
2006-03-20 21:03 ` Matheus Izvekov
2006-03-20 21:22 ` Jan Engelhardt
2006-03-20 22:02 ` Nick Warne [this message]
2006-03-20 22:37 ` Chris Boot
2006-03-20 21:02 ` J. Bruce Fields
2006-03-21 11:16 ` Alan Cox
2006-03-21 17:45 ` [PATCH] " Jan Engelhardt
2006-03-22 9:32 ` 祁勇
2006-03-21 0:06 ` Nigel Cunningham
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=7c3341450603201402k54b0cd6cy@mail.gmail.com \
--to=nick@linicks.net \
--cc=bootc@bootc.net \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mizvekov@gmail.com \
--cc=pavel@ucw.cz \
/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