From: Randy Dunlap <rdunlap@xenotime.net>
To: Joe Perches <joe@perches.com>
Cc: Andrew Murray <amurray@mpcdata.com>,
w.sang@pengutronix.de, geert@linux-m68k.org,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org,
trivial@kernel.org, udknight@gmail.com, namhyung@gmail.com,
Andrew Murray <amurray@mpc-data.co.uk>
Subject: Re: [PATCH] printk-formats.txt documentation update
Date: Thu, 9 Jun 2011 15:37:42 -0700 [thread overview]
Message-ID: <20110609153742.2ad54aaa.rdunlap@xenotime.net> (raw)
In-Reply-To: <1307656829.13329.53.camel@Joe-Laptop>
On Thu, 09 Jun 2011 15:00:29 -0700 Joe Perches wrote:
> On Thu, 2011-06-09 at 14:51 -0700, Randy Dunlap wrote:
> > On Thu, 9 Jun 2011 22:24:48 +0100 Andrew Murray wrote:
> > > + For printing-16 byte UUID/GUIDs addresses. The additional 'l', 'L',
> > For printing 16-byte
> > You want to resend or shall I just fix it?
>
> Hey Randy.
>
> I find your seeming insistence on using a dash
> between the numeric count and the word byte to
> be a bit odd.
>
> Stylistically, why do you want it there?
Mostly to make it clear. It's too easy to be ambiguous.
> cheers, Joe
Without hyphen:
For printing 16 byte UUID/GUIDs addresses.
Those adjectives are confusing. I don't know what that phrase means.
It could easily mean 16 UUID/GUIDs, but it's ambiguous.
But
For printing 16-byte UUID/GUIDs addresses.
That means (clearly to me) that UUID/GUIDs are 16-byte entities.
Or see www.incredibleenglish.com/pdf/Hyphens.pdf, section 1,
"Hyphenate unit modifiers."
Or see http://www.ehow.com/how_4473498_use-hyphen-sentence.html, section 1,
"Link compound modifiers with hyphens."
Or see http://www.getitwriteonline.com/archive/040201HyphAdj.htm
HTH.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-06-09 22:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 0:15 [PATCH] printk-formats.txt documentation update Andrew Murray
2011-02-06 0:27 ` Tim Bird
2011-02-06 0:37 ` Joe Perches
2011-02-06 10:07 ` Andrew Murray
2011-02-06 10:16 ` Geert Uytterhoeven
2011-02-06 16:14 ` Andrew Murray
2011-02-06 16:23 ` Andrew Murray
2011-02-07 9:29 ` Wolfram Sang
2011-02-07 18:12 ` Andrew Murray
2011-02-07 19:33 ` Joe Perches
2011-02-11 8:15 ` Andrew Murray
2011-06-09 17:33 ` [PATCH] Revised patch Andrew Murray
2011-06-09 17:40 ` Joe Perches
2011-06-09 17:47 ` Namhyung Kim
2011-06-09 17:48 ` Andrew Murray
2011-06-09 18:04 ` [PATCH] printk-formats.txt documentation update Andrew Murray
2011-06-09 18:20 ` Namhyung Kim
2011-06-09 18:55 ` Andrew Murray
2011-06-09 19:45 ` Randy Dunlap
2011-06-09 21:24 ` Andrew Murray
2011-06-09 21:51 ` Randy Dunlap
2011-06-09 22:00 ` Joe Perches
2011-06-09 22:21 ` Andrew Murray
2011-06-09 22:37 ` Randy Dunlap [this message]
2011-06-09 22:53 ` Joe Perches
2011-06-09 22:57 ` Randy Dunlap
2011-06-10 17:50 ` Randy Dunlap
2011-06-10 17:56 ` Andrew Murray
2011-06-09 17:47 ` [PATCH] Revised patch Randy Dunlap
2011-06-09 17:53 ` Joe Perches
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=20110609153742.2ad54aaa.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=amurray@mpc-data.co.uk \
--cc=amurray@mpcdata.com \
--cc=geert@linux-m68k.org \
--cc=joe@perches.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--cc=trivial@kernel.org \
--cc=udknight@gmail.com \
--cc=w.sang@pengutronix.de \
/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).