From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Questions about git-rev-parse
Date: Tue, 27 Feb 2007 21:52:58 -0500 [thread overview]
Message-ID: <20070228025258.GD2178@thunk.org> (raw)
In-Reply-To: <7vvehn2eds.fsf@assigned-by-dhcp.cox.net>
On Tue, Feb 27, 2007 at 06:40:47PM -0800, Junio C Hamano wrote:
> You are lacking historical context that our porcelain-ish were
So while I'm asking questions, where did the "*-ish" terminology come
from, anyway? For someone who is a relative newbie, terms like
tree-ish and commit-ish seems like some kind of strange, git jargon.
And this is the first time I've come across porcelian-ish.
I had the mental model (which I had intuited, since no git
documentation I could find had bothered to explain it) that -ish meant
something like specifier, so "tree-ish" meant tree specifier, so a
commit id could get dereferenced into a tree id, so it could be used
to specify a tree.
But that explanation doesn't explain "porcelain-ish".
So what does -ish mean, really? Where did it come from? And if it
does add value to use this wierd bit of git jargon, can we document it
somewhere, preferably in a tutorial and main git man page? It used in
too many places that it's probably not worth it to rip it out, but I
can tell you that for someone who is learning git from the ground up,
it would be easier if we used some term like <tree_specifier> instead
of <tree-ish>.
Regards,
- Ted
next prev parent reply other threads:[~2007-02-28 2:53 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 [this message]
2007-02-28 3:33 ` Linus Torvalds
2007-02-28 6:40 ` Theodore Tso
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=20070228025258.GD2178@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).