1GIT-LS-TREE(1) Git Manual GIT-LS-TREE(1)
2
6 git-ls-tree - List the contents of a tree object
7
9 git ls-tree [-d] [-r] [-t] [-l] [-z]
10 [--name-only] [--name-status] [--full-name] [--full-tree] [--abbrev=[<n>]]
11 <tree-ish> [paths...]
12
15 Lists the contents of a given tree object, like what "/bin/ls -a" does
16 in the current working directory. Note that:
17 · the behaviour is slightly different from that of "/bin/ls" in that
19 the paths denote just a list of patterns to match, e.g. so
20 specifying directory name (without -r) will behave differently, and
21 order of the arguments does not matter.
22 · the behaviour is similar to that of "/bin/ls" in that the paths is
24 taken as relative to the current working directory. E.g. when you
25 are in a directory sub that has a directory dir, you can run git
26 ls-tree -r HEAD dir to list the contents of the tree (that is
27 sub/dir in HEAD). You don’t want to give a tree that is not at the
28 root level (e.g. git ls-tree -r HEAD:sub dir) in this case, as
29 that would result in asking for sub/sub/dir in the HEAD commit.
30 However, the current working directory can be ignored by passing
31 --full-tree option.
32
34 <tree-ish>
35 Id of a tree-ish.
36 -d
38 Show only the named tree entry itself, not its children.
39 -r
41 Recurse into sub-trees.
42 -t
44 Show tree entries even when going to recurse them. Has no effect if
45 -r was not passed. -d implies -t.
46 -l, --long
48 Show object size of blob (file) entries.
49 -z
51 \0 line termination on output.
52 --name-only, --name-status
54 List only filenames (instead of the "long" output), one per line.
55 --abbrev[=<n>]
57 Instead of showing the full 40-byte hexadecimal object lines, show
58 only a partial prefix. Non default number of digits can be
59 specified with --abbrev=<n>.
60 --full-name
62 Instead of showing the path names relative to the current working
63 directory, show the full path names.
64 --full-tree
66 Do not limit the listing to the current working directory. Implies
67 --full-name.
68 paths
70 When paths are given, show them (note that this isn’t really raw
71 pathnames, but rather a list of patterns to match). Otherwise
72 implicitly uses the root level of the tree as the sole path
73 argument.
74
76 <mode> SP <type> SP <object> TAB <file>
77 Unless the -z option is used, TAB, LF, and backslash characters in
79 pathnames are represented as \t, \n, and \\, respectively. This output
80 format is compatible with what --index-info --stdin of git update-index
81 expects.
82 When the -l option is used, format changes to
84 <mode> SP <type> SP <object> SP <object size> TAB <file>
86 Object size identified by <object> is given in bytes, and
88 right-justified with minimum width of 7 characters. Object size is
89 given only for blobs (file) entries; for other entries - character is
90 used in place of size.
91
93 Written by Petr Baudis <pasky@suse.cz[1]> Completely rewritten from
94 scratch by Junio C Hamano <gitster@pobox.com[2]>, another major rewrite
95 by Linus Torvalds <torvalds@osdl.org[3]>
96
98 Documentation by David Greaves, Junio C Hamano and the git-list
99 <git@vger.kernel.org[4]>.
100
102 Part of the git(1) suite
103
105 1. pasky@suse.cz
106 mailto:pasky@suse.cz
107 2. gitster@pobox.com
109 mailto:gitster@pobox.com
110 3. torvalds@osdl.org
112 mailto:torvalds@osdl.org
113 4. git@vger.kernel.org
115 mailto:git@vger.kernel.org
116Git 1.7.1 08/16/2017 GIT-LS-TREE(1)