From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Edit user manual for grammar
Date: Tue, 12 Jun 2007 16:05:25 -0400 [thread overview]
Message-ID: <20070612200525.GC2383@fieldses.org> (raw)
In-Reply-To: <200706122028.01310.andyparkins@gmail.com>
On Tue, Jun 12, 2007 at 08:27:59PM +0100, Andy Parkins wrote:
> It's certainly common, I don't think that it's correct though.
In cases like this some seem to think it's actually required:
"Use a hyphen to connect two or more words functioning together
as an adjective before a noun."
(From p. 234 of "A Writer's Reference", 3rd ed., Diana Hacker--just what
I happen to have on my shelf.) I suppose it's there to help find the
modified noun when you're constructing modifiers out of multiple words
that aren't necessarily adjectives.
But whatever, I've no real objection to the patch.
> Please don't take "vulgar" to mean disgusting, I meant "common". Sorry
> if that was offensive.
Nah, just curious. "For" seems a little more precise in this case, so
fair enough.
> > 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? ;-)
Hah. OK, next suggestion....
--b.
next prev parent reply other threads:[~2007-06-12 20:05 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
2007-06-12 20:05 ` J. Bruce Fields [this message]
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=20070612200525.GC2383@fieldses.org \
--to=bfields@fieldses.org \
--cc=andyparkins@gmail.com \
--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).