Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-write-tree(1) [suse man page]

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

git-write-tree - Create a tree object from the current index SYNOPSIS
git write-tree [--missing-ok] [--prefix=<prefix>/] DESCRIPTION
Creates a tree object using the current index. The name of the new tree object is printed to standard output. The index must be in a fully merged state. Conceptually, git write-tree sync()s the current index contents into a set of tree files. In order to have that match what is actually in your directory right now, you need to have done a git update-index phase before you did the git write-tree. OPTIONS
--missing-ok Normally git write-tree ensures that the objects referenced by the directory exist in the object database. This option disables this check. --prefix=<prefix>/ Writes a tree object that represents a subdirectory <prefix>. This can be used to write the tree object for a subproject that is in the named subdirectory. AUTHOR
Written by Linus Torvalds <[1]> DOCUMENTATION
Documentation by David Greaves, Junio C Hamano and the git-list <[2]>. GIT
Part of the git(1) suite NOTES
1. 2. Git 1.7.1 07/05/2010 GIT-WRITE-TREE(1)

Check Out this Related Man Page

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

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> [paths...] 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 paths denote 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 paths 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. paths 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. AUTHOR
Written by Petr Baudis <[1]> Completely rewritten from scratch by Junio C Hamano <[2]>, another major rewrite by Linus Torvalds <[3]> DOCUMENTATION
Documentation by David Greaves, Junio C Hamano and the git-list <[4]>. GIT
Part of the git(1) suite NOTES
1. 2. 3. 4. Git 1.7.1 07/05/2010 GIT-LS-TREE(1)
Man Page

Featured Tech Videos