8523b1e355
This could be a localization issue, but we had about four dozen "normalize"s (or variants, e.g. normalized, renormalize, etc.), and only one "normalised" (no other variants), so normalize normalised into normalized. Signed-off-by: Elijah Newren <newren@gmail.com> Reviewed-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
41 lines
1.1 KiB
Plaintext
41 lines
1.1 KiB
Plaintext
git-mktree(1)
|
|
=============
|
|
|
|
NAME
|
|
----
|
|
git-mktree - Build a tree-object from ls-tree formatted text
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'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 normalized 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.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|