6 git-commit-tree - Create a new commit object
11 'git-commit-tree' <tree> [-p <parent commit>]\* < changelog
15 This is usually not what an end user wants to run directly. See
16 gitlink:git-commit[1] instead.
18 Creates a new commit object based on the provided tree object and
19 emits the new commit object id on stdout. If no parent is given then
20 it is considered to be an initial tree.
22 A commit object usually has 1 parent (a commit after a change) or up
23 to 16 parents. More than one parent represents a merge of branches
26 While a tree represents a particular directory state of a working
27 directory, a commit represents that state in "time", and explains how
30 Normally a commit would identify a new "HEAD" state, and while git
31 doesn't care where you save the note about that state, in practice we
32 tend to just write the result to the file that is pointed at by
33 `.git/HEAD`, so that we can always see what the last committed
39 An existing tree object
42 Each '-p' indicates the id of a parent commit object.
48 A commit encapsulates:
50 - all parent object ids
51 - author name, email and date
52 - committer name and email and the commit time.
54 If not provided, "git-commit-tree" uses your name, hostname and domain to
55 provide author and committer info. This can be overridden by
56 either `.git/config` file, or using the following environment variables.
65 (nb "<", ">" and "\n"s are stripped)
67 In `.git/config` file, the following items are used for GIT_AUTHOR_NAME and
72 email = "your@email.address.xz"
74 A commit comment is read from stdin (max 999 chars). If a changelog
75 entry is not provided via "<" redirection, "git-commit-tree" will just wait
76 for one to be entered and terminated with ^D.
81 You don't exist. Go away!::
82 The passwd(5) gecos field couldn't be read
83 Your parents must have hated you!::
84 The password(5) gecos field is longer than a giant static buffer.
85 Your sysadmin must hate you!::
86 The password(5) name field is longer than a giant static buffer.
95 gitlink:git-write-tree[1]
100 Written by Linus Torvalds <torvalds@osdl.org>
104 Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.
108 Part of the gitlink:git[7] suite