git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Questions about git-rev-parse
Date: Wed, 28 Feb 2007 01:40:36 -0500	[thread overview]
Message-ID: <20070228064036.GF2178@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702271921110.12485@woody.linux-foundation.org>

On Tue, Feb 27, 2007 at 07:33:03PM -0800, Linus Torvalds wrote:
> No, it really is English. At least grammatically.
> 
> A "tree-ish" is "like a tree", exactly like "sheepish" is "like a sheep". 
> Nothing really git-specific about it, except for it certainly having 
> become common usage in a way that it may not be normally ;)

Well, in the randomhouse web page you quoted:

	Our -ish is a suffix that forms adjectives from nouns or other
	adjectives. Some of the senses existed in Old English (then
	spelled -isc but pronounced the same way), such as 'of, being,
	or pertaining to', used to form adjectives indicating a
	national, ethnic, or religious origin (British, Jewish).

it claims that the -ish suffix forms an _adjective_.   But in the sense of

	git describe <committish>

In the git world we are using "committish" (and in the documentation
sometimes we use committish and treeish, and other times we use
commit-ish and tree-ish) as a _noun_, and not an adjective.  So I'm
still going to take a bit of issue that it's grammatical English, and
I still think that "tree_specifier" and "commit_specifier" would have
been clearer.

In any case, I note that in the git(7) man page, there is a formal
definition of tree-ish, but not of commit-ish.  Would this patch to
Documentation/git.txt be correct?

diff --git a/Documentation/git.txt b/Documentation/git.txt
index 9a74747..ff693c3 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -241,6 +241,12 @@ Identifier Terminology
 	operate on a <tree> object but automatically dereferences
 	<commit> and <tag> objects that point at a <tree>.
 
+<commit-ish>::
+	Indicates a commit or tag object name.  A
+	command that takes a <commit-ish> argument ultimately wants to
+	operate on a <commit> object but automatically dereferences
+	<tag> objects that point at a <commit>.
+
 <type>::
 	Indicates that an object type is required.
 	Currently one of: `blob`, `tree`, `commit`, or `tag`.

							- Ted

  reply	other threads:[~2007-02-28  6:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28  2:23 Questions about git-rev-parse Theodore Ts'o
2007-02-28  2:40 ` Junio C Hamano
2007-02-28  2:52   ` Theodore Tso
2007-02-28  3:33     ` Linus Torvalds
2007-02-28  6:40       ` Theodore Tso [this message]
2007-02-28  8:54       ` Andy Parkins
2007-02-28 16:00         ` Linus Torvalds
2007-02-28  3:19 ` Linus Torvalds
2007-03-01  2:16   ` Willhelm Busch

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=20070228064036.GF2178@thunk.org \
    --to=tytso@mit.edu \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@linux-foundation.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).