From: Eric Sunshine <sunshine@sunshineco.com>
To: Jeff King <peff@peff.net>
Cc: "Thomas Rast" <trast@inf.ethz.ch>,
"Thomas Rast" <trast@student.ethz.ch>,
"Git List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Bo Yang" <struggleyb.nku@gmail.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Will Palmer" <wmpalmer@gmail.com>
Subject: Re: [PATCH v9 5/5] Speed up log -L... -M
Date: Sun, 24 Mar 2013 03:38:54 -0400 [thread overview]
Message-ID: <CAPig+cSnndjHWJ3U-DE3qG9Q3VvuDgyFnnfwZ8m3K335nwFCwQ@mail.gmail.com> (raw)
In-Reply-To: <20130323090459.GB25600@sigill.intra.peff.net>
On Sat, Mar 23, 2013 at 5:04 AM, Jeff King <peff@peff.net> wrote:
> On Sat, Mar 23, 2013 at 06:58:48AM +0100, Thomas Rast wrote:
>> Eric Sunshine <sunshine@sunshineco.com> writes:
>> > On Thu, Mar 21, 2013 at 8:52 AM, Thomas Rast <trast@student.ethz.ch> wrote:
>> >> This is a bit hacky and should really be replaced by equivalent
>> >> support in --follow, and just using that. However, in the meantime it
>> >
>> > s/using/use/
>>
>> I'm not a native speaker, but I really think 'using' is more correct
>> here.
>
> Cannot...resist...grammar discussion.
>
> I think you are both potentially right.
>
> You might consider the two items "equivalent support" and "using that"
> to be two noun phrases that are objects of the preposition "by", and
> that the writer simply omits the second "by" after the "and". In which
> case you are making a noun phrase from a verb phrase, and would want to
> use the gerund form "using". And the sentence, simplifying out some
> modifiers and adding the missing "by" (which is fine to omit, but the
> parts of speech become much clearer with it there), looks like:
>
> ...should be replaced by equivalent support, and by using that.
>
> However, you could also argue that the final clause is a second verb
> phrase for "this should" which just omits the extra "should" (which is
> also OK in a list. In which case "use" acts as a verb, and parses as:
>
> ...should be replaced by equivalent support, and this should just use
> that.
>
> So I think it is correct either way, and though it parses slightly
> differently, the overall meaning is the same.
>
> Phew. Totally not worth that much discussion, but for some reason I find
> these sorts of ambiguous language cases interesting.
Wishing to avoid bike-shedding the commit message, I suggested
s/using/use/ as a minor change to help clarify the grammar a bit.
However, perhaps it could be rephrased as:
This is a bit hacky and should really be replaced by equivalent
support in --follow, which can then be employed instead.
-- ES
next prev parent reply other threads:[~2013-03-24 7:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 12:52 [PATCH v9 0/5] git log -L Thomas Rast
2013-03-21 12:52 ` [PATCH v9 1/5] Refactor parse_loc Thomas Rast
2013-03-21 12:52 ` [PATCH v9 2/5] Export rewrite_parents() for 'log -L' Thomas Rast
2013-03-21 12:52 ` [PATCH v9 3/5] Implement line-history search (git log -L) Thomas Rast
2013-03-21 19:05 ` Junio C Hamano
2013-03-23 6:00 ` Thomas Rast
2013-03-21 12:52 ` [PATCH v9 4/5] log -L: :pattern:file syntax to find by funcname Thomas Rast
2013-03-21 12:52 ` [PATCH v9 5/5] Speed up log -L... -M Thomas Rast
2013-03-21 21:11 ` Eric Sunshine
2013-03-23 5:58 ` Thomas Rast
2013-03-23 9:04 ` Jeff King
2013-03-24 7:38 ` Eric Sunshine [this message]
2013-03-23 6:44 ` [PATCH v9a 0/5] git log -L Thomas Rast
2013-03-23 6:44 ` [PATCH v9a 1/5] Refactor parse_loc Thomas Rast
2013-03-23 6:44 ` [PATCH v9a 2/5] Export rewrite_parents() for 'log -L' Thomas Rast
2013-03-23 6:44 ` [PATCH v9a 3/5] Implement line-history search (git log -L) Thomas Rast
2013-03-23 10:31 ` Antoine Pelisse
2013-03-23 10:32 ` Antoine Pelisse
2013-03-28 16:47 ` [PATCH v10 0/5] git log -L Thomas Rast
2013-03-28 16:47 ` [PATCH v10 1/5] Refactor parse_loc Thomas Rast
2013-03-28 16:47 ` [PATCH v10 2/5] Export rewrite_parents() for 'log -L' Thomas Rast
2013-03-28 16:47 ` [PATCH v10 3/5] Implement line-history search (git log -L) Thomas Rast
2013-03-28 16:47 ` [PATCH v10 4/5] log -L: :pattern:file syntax to find by funcname Thomas Rast
2013-03-28 16:47 ` [PATCH v10 5/5] Speed up log -L... -M Thomas Rast
2013-03-23 6:44 ` [PATCH v9a 4/5] log -L: :pattern:file syntax to find by funcname Thomas Rast
2013-03-23 6:44 ` [PATCH v9a 5/5] Speed up log -L... -M Thomas Rast
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=CAPig+cSnndjHWJ3U-DE3qG9Q3VvuDgyFnnfwZ8m3K335nwFCwQ@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=struggleyb.nku@gmail.com \
--cc=trast@inf.ethz.ch \
--cc=trast@student.ethz.ch \
--cc=wmpalmer@gmail.com \
--cc=zbyszek@in.waw.pl \
/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).