From: Bruce Korb <bruce.korb@gmail.com>
To: git@vger.kernel.org
Subject: Documentation problems
Date: Sun, 20 Sep 2009 10:58:36 -0700 [thread overview]
Message-ID: <4AB66D4C.70301@gmail.com> (raw)
Hi,
I'm trying to figure out what a ``tree-ish''.
I cannot seem to use many of the commands until I know.
<tree-ish>
Indicates a tree, commit or tag object name. A command that takes a
<tree-ish> argument ultimately wants to operate on a <tree> object
but automatically dereferences <commit> and <tag> objects that point at a <tree>.
I need a translation. :( Thank you. Regards, Bruce
P.S. I have a SuSE installation with everything relating to GIT installed.
The man pages reference commands like, "git-ls-tree --name-only" except
that there isn't any such command. Unless you reverse engineer the
implementation of "git", discover the /usr/lib/git directory and add it
to your path. That hassle is rather inconvenient. More hints about
where the git commands get squirreled away would be useful. Thank you.
next reply other threads:[~2009-09-20 17:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 17:58 Bruce Korb [this message]
2009-09-20 18:24 ` Documentation problems Matthieu Moy
2009-09-20 18:37 ` Bruce Korb
2009-09-20 18:45 ` Matthieu Moy
2009-09-20 20:52 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2011-11-27 2:40 Tom Rini
2011-11-27 14:29 ` Paul Eggleton
2011-11-27 15:53 ` Chris Larson
2011-11-27 16:58 ` Frans Meulenbroeks
2011-11-27 17:06 ` Paul Eggleton
2011-11-27 18:38 ` Paul Menzel
2011-11-27 18:56 ` Paul Eggleton
2011-11-27 19:06 ` Paul Menzel
2011-11-27 21:49 ` Frans Meulenbroeks
2011-11-27 22:00 ` Paul Menzel
2011-11-27 15:44 ` Koen Kooi
2011-11-28 5:11 ` Tom Rini
2011-11-28 6:36 ` Chris Verges
2011-11-28 9:23 ` Koen Kooi
2011-11-28 12:19 ` Denis 'GNUtoo' Carikli
2011-11-28 13:40 ` Paul Eggleton
2011-11-28 14:40 ` Samuel Stirtzel
2011-11-28 10:30 ` Phil Blundell
2011-11-28 11:07 ` Richard Purdie
2011-11-28 11:16 ` Otavio Salvador
2011-11-28 13:33 ` Philip Balister
2011-11-28 13:36 ` Philip Balister
2011-11-28 14:06 ` Koen Kooi
2011-11-28 18:02 ` Bernhard Guillon
2011-11-28 21:13 ` Tom Rini
2011-11-29 8:24 ` Frans Meulenbroeks
2011-11-29 20:17 ` Khem Raj
2011-11-29 21:46 ` Frans Meulenbroeks
2011-11-29 23:37 ` Tom Rini
2011-11-30 7:06 ` Frans Meulenbroeks
2011-11-28 17:44 ` Bernhard Guillon
2011-12-07 5:01 ` Bill Traynor
2011-12-07 22:17 ` Khem Raj
2011-11-30 15:49 ` Rainer Koenig
2011-11-30 17:06 ` Koen Kooi
2011-11-30 17:32 ` McClintock Matthew-B29882
2011-11-30 18:46 ` Paul Menzel
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=4AB66D4C.70301@gmail.com \
--to=bruce.korb@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.