git-mktree(1) [suse man page]

GIT-MKTREE(1)							    Git Manual							     GIT-MKTREE(1)

NAME

       git-mktree - Build a tree-object from ls-tree formatted text

SYNOPSIS

       git mktree [-z] [--missing] [--batch]

DESCRIPTION

       Reads standard input in non-recursive ls-tree output format, and creates a tree object. The order of the tree entries is normalised by
       mktree so pre-sorting the input is not required. The object name of the tree object built is written to the standard output.

OPTIONS

       -z
	   Read the NUL-terminated ls-tree -z output instead.

       --missing
	   Allow missing objects. The default behaviour (without this option) is to verify that each tree entry's sha1 identifies an existing
	   object. This option has no effect on the treatment of gitlink entries (aka "submodules") which are always allowed to be missing.

       --batch
	   Allow building of more than one tree object before exiting. Each tree is separated by as single blank line. The final new-line is
	   optional. Note - if the -z option is used, lines are terminated with NUL.

AUTHOR

       Written by Junio C Hamano <gitster@pobox.com[1]>

DOCUMENTATION

       Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>.

GIT

       Part of the git(1) suite

NOTES

	1. gitster@pobox.com
	   mailto:gitster@pobox.com

	2. git@vger.kernel.org
	   mailto:git@vger.kernel.org

Git 1.7.1							    07/05/2010							     GIT-MKTREE(1)

GIT-HASH-OBJECT(1)						    Git Manual							GIT-HASH-OBJECT(1)

NAME

       git-hash-object - Compute object ID and optionally creates a blob from a file

SYNOPSIS

       git hash-object [-t <type>] [-w] [--path=<file>|--no-filters] [--stdin] [--] <file>...
       git hash-object [-t <type>] [-w] --stdin-paths [--no-filters] < <list-of-paths>

DESCRIPTION

       Computes the object ID value for an object with specified type with the contents of the named file (which can be outside of the work tree),
       and optionally writes the resulting object into the object database. Reports its object ID to its standard output. This is used by git
       cvsimport to update the index without modifying files in the work tree. When <type> is not specified, it defaults to "blob".

OPTIONS

       -t <type>
	   Specify the type (default: "blob").

       -w
	   Actually write the object into the object database.

       --stdin
	   Read the object from standard input instead of from a file.

       --stdin-paths
	   Read file names from stdin instead of from the command-line.

       --path
	   Hash object as it were located at the given path. The location of file does not directly influence on the hash value, but path is used
	   to determine what git filters should be applied to the object before it can be placed to the object database, and, as result of
	   applying filters, the actual blob put into the object database may differ from the given file. This option is mainly useful for hashing
	   temporary files located outside of the working directory or files read from stdin.

       --no-filters
	   Hash the contents as is, ignoring any input filter that would have been chosen by the attributes mechanism, including crlf conversion.
	   If the file is read from standard input then this is always implied, unless the --path option is given.

AUTHOR

       Written by Junio C Hamano <gitster@pobox.com[1]>

DOCUMENTATION

       Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org[2]>.

GIT

       Part of the git(1) suite

NOTES

	1. gitster@pobox.com
	   mailto:gitster@pobox.com

	2. git@vger.kernel.org
	   mailto:git@vger.kernel.org

Git 1.7.1							    07/05/2010							GIT-HASH-OBJECT(1)