0b444cdb19
The documentation was quite inconsistent when spelling 'git cmd' if it
only refers to the program, not to some specific invocation syntax:
both 'git-cmd' and 'git cmd' spellings exist.
The current trend goes towards dashless forms, and there is precedent
in 647ac70 (git-svn.txt: stop using dash-form of commands.,
2009-07-07) to actively eliminate the dashed variants.
Replace 'git-cmd' with 'git cmd' throughout, except where git-shell,
git-cvsserver, git-upload-pack, git-receive-pack, and
git-upload-archive are concerned, because those really live in the
$PATH.
51 lines
1.2 KiB
Plaintext
51 lines
1.2 KiB
Plaintext
git-write-tree(1)
|
|
=================
|
|
|
|
NAME
|
|
----
|
|
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 <torvalds@osdl.org>
|
|
|
|
Documentation
|
|
--------------
|
|
Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|