From: Jeff King <peff@peff.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Junio C Hamano <junkio@cox.net>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: Clueless bisect error message
Date: Wed, 11 Oct 2006 14:04:49 -0400 [thread overview]
Message-ID: <20061011180449.GA2897@coredump.intra.peff.net> (raw)
In-Reply-To: <m3ejtfvwvi.fsf@defiant.localdomain>
On Wed, Oct 11, 2006 at 02:51:29PM +0200, Krzysztof Halasa wrote:
> > + die "You can't bisect a seeked tree!"
> Just to make sure: dictionary.reference.com doesn't know the
> "seeked" word (I don't either though that may be normal).
>
> Should it read "sought"? Not sure what does the message talk about.
Seeked is not a "real" word in the sense of being in any dictionary. The
past participle form of "seek" is indeed "sought" (though one might want
to use the passive perfect participle form "being sought" for this
case).
However, the use of the word "sought" implies to me the classical
definition of the word seek: "to look for something." The definition we
are using here is a more modern, computer-oriented definition: "to move
to a position within an ordered set" (since we are referring to Cogito's
cg-seek command). Just as you might verbify (another non-word!) a
command and say "I catted those files together", the tree has been
"seeked." One could argue it should be "cat'd" and "seek'd" to indicate
their non-word status, but that idiom is common enough among
programmers, especially Unix users, that I suspect it will make sense
either way.
At any rate, the word "seeked" was in the original error message, so I
didn't introduce it. Are other people bothered by it?
-Peff
prev parent reply other threads:[~2006-10-11 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 7:08 Clueless bisect error message Nguyen Thai Ngoc Duy
2006-10-11 7:22 ` Junio C Hamano
2006-10-11 7:50 ` Nguyen Thai Ngoc Duy
2006-10-11 8:11 ` Junio C Hamano
2006-10-11 8:30 ` Nguyen Thai Ngoc Duy
2006-10-11 9:14 ` Jeff King
2006-10-11 12:51 ` Krzysztof Halasa
2006-10-11 18:04 ` Jeff King [this message]
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=20061011180449.GA2897@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=khc@pm.waw.pl \
--cc=pclouds@gmail.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).