git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Symonds" <dsymonds@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Wincent Colaiuta" <win@wincent.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] Grammar fixes for gitattributes documentation
Date: Thu, 15 Nov 2007 18:20:10 +1100	[thread overview]
Message-ID: <ee77f5c20711142320x1a070b21xf00f0853fe09e34c@mail.gmail.com> (raw)
In-Reply-To: <20071115071558.GE10185@sigill.intra.peff.net>

On Nov 15, 2007 6:15 PM, Jeff King <peff@peff.net> wrote:
> On Wed, Nov 14, 2007 at 10:04:25AM +0100, Wincent Colaiuta wrote:
>
> >>> +A `filter` attribute can be set to a string value which names a
> >>> filter driver specified in the configuration.
> >>
> >> Will we get the canned "which vs that" discussion on this change?
> >
> > Perhaps. Neither would be incorrect, although technically "that" is a
> > tighter match.
>
> Really? I would think "which" works better, in that it is not
> restrictive. I.e., "The filter attribute is set to a string. This
> string, btw, names a filter driver" (which) rather than "The filter
> attribute is set to a string, and from the set of strings, it is set to
> the particular string that names a filter driver" (that).

"that" should be used to introduce restrictive clauses (as you point
out), and this use should be a restrictive clause, since you can't set
the attribute to just any value--you need to set it to the value
*that* names the desired filter driver.


Dave.
... writing a thesis, so has grammar on the brain.

  reply	other threads:[~2007-11-15  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  7:51 [PATCH] Grammar fixes for gitattributes documentation Wincent Colaiuta
2007-11-14  8:55 ` Junio C Hamano
2007-11-14  9:04   ` Wincent Colaiuta
2007-11-14  9:27     ` Junio C Hamano
2007-11-15  7:15     ` Jeff King
2007-11-15  7:20       ` David Symonds [this message]
2007-11-15  7:27         ` Jeff King

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=ee77f5c20711142320x1a070b21xf00f0853fe09e34c@mail.gmail.com \
    --to=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=win@wincent.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;
as well as URLs for NNTP newsgroup(s).