]> git.ipfire.org Git - thirdparty/git.git/blame - Documentation/git-commit-tree.txt
commit-tree: document -S option consistently
[thirdparty/git.git] / Documentation / git-commit-tree.txt
CommitLineData
2cf565c5
DG
1git-commit-tree(1)
2==================
2cf565c5
DG
3
4NAME
5----
c3f0baac 6git-commit-tree - Create a new commit object
2cf565c5
DG
7
8
9SYNOPSIS
10--------
7791a1d9 11[verse]
96b8d93a 12'git commit-tree' <tree> [(-p <parent>)...] < changelog
df45cb3e
BK
13'git commit-tree' [(-p <parent>)...] [-S[<keyid>]] [(-m <message>)...]
14 [(-F <file>)...] <tree>
15
2cf565c5
DG
16
17DESCRIPTION
18-----------
5cb545fa 19This is usually not what an end user wants to run directly. See
5162e697 20linkgit:git-commit[1] instead.
5cb545fa 21
2cf565c5 22Creates a new commit object based on the provided tree object and
96b8d93a
JH
23emits the new commit object id on stdout. The log message is read
24from the standard input, unless `-m` or `-F` options are given.
2cf565c5 25
b3bc97cb
TR
26A commit object may have any number of parents. With exactly one
27parent, it is an ordinary commit. Having more than one parent makes
28the commit a merge between several lines of history. Initial (root)
29commits have no parents.
2cf565c5
DG
30
31While a tree represents a particular directory state of a working
32directory, a commit represents that state in "time", and explains how
33to get there.
34
2de9b711 35Normally a commit would identify a new "HEAD" state, and while Git
2cf565c5 36doesn't care where you save the note about that state, in practice we
27dedf0c
JH
37tend to just write the result to the file that is pointed at by
38`.git/HEAD`, so that we can always see what the last committed
39state was.
2cf565c5
DG
40
41OPTIONS
42-------
43<tree>::
44 An existing tree object
45
96b8d93a 46-p <parent>::
f73ae1fc 47 Each '-p' indicates the id of a parent commit object.
a6080a0a 48
96b8d93a 49-m <message>::
b4ab1980 50 A paragraph in the commit log message. This can be given more than
96b8d93a
JH
51 once and each <message> becomes its own paragraph.
52
53-F <file>::
54 Read the commit log message from the given file. Use `-` to read
55 from the standard input.
56
df45cb3e
BK
57-S[<keyid>]::
58 GPG-sign commit.
59
2cf565c5
DG
60
61Commit Information
62------------------
63
64A commit encapsulates:
65
66- all parent object ids
67- author name, email and date
68- committer name and email and the commit time.
69
0734d265 70While parent object ids are provided on the command line, author and
02783075 71committer information is taken from the following environment variables,
0734d265 72if set:
2cf565c5
DG
73
74 GIT_AUTHOR_NAME
75 GIT_AUTHOR_EMAIL
76 GIT_AUTHOR_DATE
77 GIT_COMMITTER_NAME
78 GIT_COMMITTER_EMAIL
4e58bf97 79 GIT_COMMITTER_DATE
2cf565c5 80
df8baa42 81(nb "<", ">" and "\n"s are stripped)
2cf565c5 82
0734d265
MH
83In case (some of) these environment variables are not set, the information
84is taken from the configuration items user.name and user.email, or, if not
be33414b
PE
85present, the environment variable EMAIL, or, if that is not set,
86system user name and the hostname used for outgoing mail (taken
8a55caa8
JN
87from `/etc/mailname` and falling back to the fully qualified hostname when
88that file does not exist).
5773c9f2 89
a82830a4 90A commit comment is read from stdin. If a changelog
0b444cdb 91entry is not provided via "<" redirection, 'git commit-tree' will just wait
df8baa42 92for one to be entered and terminated with ^D.
2cf565c5 93
788070a2 94include::date-formats.txt[]
5773c9f2 95
5dc7bcc2
JH
96Discussion
97----------
98
99include::i18n.txt[]
100
8a55caa8
JN
101FILES
102-----
103/etc/mailname
104
56ae8df5 105SEE ALSO
c1bdacf9 106--------
5162e697 107linkgit:git-write-tree[1]
2cf565c5 108
2cf565c5
DG
109GIT
110---
9e1f0a85 111Part of the linkgit:git[1] suite