git-ls-tree(1) [debian man page]

GIT-LS-TREE(1)							    Git Manual							    GIT-LS-TREE(1)

NAME

       git-ls-tree - List the contents of a tree object

SYNOPSIS

       git ls-tree [-d] [-r] [-t] [-l] [-z]
		   [--name-only] [--name-status] [--full-name] [--full-tree] [--abbrev[=<n>]]
		   <tree-ish> [<path>...]

DESCRIPTION

       Lists the contents of a given tree object, like what "/bin/ls -a" does in the current working directory. Note that:

       o   the behaviour is slightly different from that of "/bin/ls" in that the <path> denotes just a list of patterns to match, e.g. so
	   specifying directory name (without -r) will behave differently, and order of the arguments does not matter.

       o   the behaviour is similar to that of "/bin/ls" in that the <path> is taken as relative to the current working directory. E.g. when you
	   are in a directory sub that has a directory dir, you can run git ls-tree -r HEAD dir to list the contents of the tree (that is sub/dir
	   in HEAD). You don't want to give a tree that is not at the root level (e.g.	git ls-tree -r HEAD:sub dir) in this case, as that would
	   result in asking for sub/sub/dir in the HEAD commit. However, the current working directory can be ignored by passing --full-tree
	   option.

OPTIONS

       <tree-ish>
	   Id of a tree-ish.

       -d
	   Show only the named tree entry itself, not its children.

       -r
	   Recurse into sub-trees.

       -t
	   Show tree entries even when going to recurse them. Has no effect if -r was not passed.  -d implies -t.

       -l, --long
	   Show object size of blob (file) entries.

       -z
	    line termination on output.

       --name-only, --name-status
	   List only filenames (instead of the "long" output), one per line.

       --abbrev[=<n>]
	   Instead of showing the full 40-byte hexadecimal object lines, show only a partial prefix. Non default number of digits can be specified
	   with --abbrev=<n>.

       --full-name
	   Instead of showing the path names relative to the current working directory, show the full path names.

       --full-tree
	   Do not limit the listing to the current working directory. Implies --full-name.

       [<path>...]
	   When paths are given, show them (note that this isn't really raw pathnames, but rather a list of patterns to match). Otherwise
	   implicitly uses the root level of the tree as the sole path argument.

OUTPUT FORMAT

	   <mode> SP <type> SP <object> TAB <file>

       Unless the -z option is used, TAB, LF, and backslash characters in pathnames are represented as 	, 
, and \, respectively. This output
       format is compatible with what --index-info --stdin of git update-index expects.

       When the -l option is used, format changes to

	   <mode> SP <type> SP <object> SP <object size> TAB <file>

       Object size identified by <object> is given in bytes, and right-justified with minimum width of 7 characters. Object size is given only for
       blobs (file) entries; for other entries - character is used in place of size.

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012							    GIT-LS-TREE(1)

Check Out this Related Man Page

GIT-TAR-TREE(1) 						    Git Manual							   GIT-TAR-TREE(1)

NAME

       git-tar-tree - Create a tar archive of the files in the named tree object

SYNOPSIS

       git tar-tree [--remote=<repo>] <tree-ish> [ <base> ]

DESCRIPTION

       THIS COMMAND IS DEPRECATED. Use git archive with --format=tar option instead (and move the <base> argument to --prefix=base/).

       Creates a tar archive containing the tree structure for the named tree. When <base> is specified it is added as a leading path to the files
       in the generated tar archive.

       git tar-tree behaves differently when given a tree ID versus when given a commit ID or tag ID. In the first case the current time is used
       as modification time of each file in the archive. In the latter case the commit time as recorded in the referenced commit object is used
       instead. Additionally the commit ID is stored in a global extended pax header. It can be extracted using git get-tar-commit-id.

OPTIONS

       <tree-ish>
	   The tree or commit to produce tar archive for. If it is the object name of a commit object.

       <base>
	   Leading path to the files in the resulting tar archive.

       --remote=<repo>
	   Instead of making a tar archive from local repository, retrieve a tar archive from a remote repository.

CONFIGURATION

       tar.umask
	   This variable can be used to restrict the permission bits of tar archive entries. The default is 0002, which turns off the world write
	   bit. The special value "user" indicates that the archiving user's umask will be used instead. See umask(2) for details.

EXAMPLES

       git tar-tree HEAD junk | (cd /var/tmp/ && tar xf -)
	   Create a tar archive that contains the contents of the latest commit on the current branch, and extracts it in /var/tmp/junk directory.

       git tar-tree v1.4.0 git-1.4.0 | gzip >git-1.4.0.tar.gz
	   Create a tarball for v1.4.0 release.

       git tar-tree v1.4.0^{tree} git-1.4.0 | gzip >git-1.4.0.tar.gz
	   Create a tarball for v1.4.0 release, but without a global extended pax header.

       git tar-tree --remote=example.com:git.git v1.4.0 >git-1.4.0.tar
	   Get a tarball v1.4.0 from example.com.

       git tar-tree HEAD:Documentation/ git-docs > git-1.4.0-docs.tar
	   Put everything in the current head's Documentation/ directory into git-1.4.0-docs.tar, with the prefix git-docs/.

GIT

       Part of the git(1) suite

Git 1.8.3.1							    06/10/2014							   GIT-TAR-TREE(1)

Linux and UNIX Man Pages

git-ls-tree(1) [debian man page]

Check Out this Related Man Page