From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [PATCH] Edit user manual for grammar
Date: Tue, 12 Jun 2007 20:27:59 +0100 [thread overview]
Message-ID: <200706122028.01310.andyparkins@gmail.com> (raw)
In-Reply-To: <20070612175421.GA26767@fieldses.org>
On Tuesday 2007, June 12, J. Bruce Fields wrote:
> On Tue, Jun 12, 2007 at 04:43:19PM +0100, Andy Parkins wrote:
> > - "last-resort" is two words, not a conjoined word, it doesn't
> > require the hyphen
>
> Right, but when you've got a couple words functioning together to
> modify a following noun, the hyphen's pretty standard: "rosy-fingered
> dawn". Is this case an exception? I suspect it's fine either way....
It's certainly common, I don't think that it's correct though. The
hyphen's is to form a new word from multiple other words; but often
these days it's just used to join two words that the author wanted
saying faster in his head. The test I always use is if the meaning
remains the same without the hyphen, it wasn't necessary.
Examples:
merry-go-round versus merry go round
editor-in-chief versus editor in chief
Both of the above loose their meaning when they don't have the hyphens.
"last-resort" doesn't need to be compound because separated it still
means "the resort that is last".
I don't say that it is a definitive _wrong_ as the meaning is not lost
nor modified; but I've always viewed English like programming - don't
add unnecessary complication.
> > - "method of" is vulgar, "method for" is nicer
>
> Reference?
Please don't take "vulgar" to mean disgusting, I meant "common". Sorry
if that was offensive.
Preposition selection and use is highly localised. I will happily
accept if you don't agree. Here is the only reference I can find, but
it is certainly not definitive, not entirely about this subject...
http://mb.sparknotes.com/mb.epl?b=2437&m=1259471&t=355765&w=1
However, it does make the case that "of" is possessive, so a "method
of ..." means "a method that belongs to ...", so to my ears "a method
for" seems the better choice.
> What we really need is a complete recovery tutorial to stick in here
> someplace. (One day git complains about a corrupt pack file. What
> do you do?) What's been stopping me from doing it, besides time, is
> no idea how to come up with a good example to work with.
A big magnet on your hard disk? ;-)
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-06-12 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 12:18 [PATCH] Edit user manual for grammer Steve Hoelzer
2007-06-12 15:43 ` [PATCH] Edit user manual for grammar Andy Parkins
2007-06-12 16:14 ` Johannes Schindelin
2007-06-12 18:55 ` Andy Parkins
2007-06-12 17:54 ` J. Bruce Fields
2007-06-12 19:27 ` Andy Parkins [this message]
2007-06-12 20:05 ` J. Bruce Fields
2007-06-13 7:17 ` David Kastrup
2007-06-12 21:08 ` Randal L. Schwartz
2007-06-13 7:15 ` David Kastrup
2007-06-13 7:39 ` Andy Parkins
2007-06-14 4:59 ` Shawn O. Pearce
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=200706122028.01310.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.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).