GIT-COMMIT-TREE(1) Git Manual GIT-COMMIT-TREE(1)NAME
git-commit-tree - Create a new commit object
SYNOPSIS
git-commit-tree <tree> [-p <parent commit>]* < changelog
DESCRIPTION
This is usually not what an end user wants to run directly. See
git-commit(1) instead.
Creates a new commit object based on the provided tree object and emits
the new commit object id on stdout. If no parent is given then it is
considered to be an initial tree.
A commit object usually has 1 parent (a commit after a change) or up to
16 parents. More than one parent represents a merge of branches that
led to them.
While a tree represents a particular directory state of a working
directory, a commit represents that state in "time", and explains how
to get there.
Normally a commit would identify a new "HEAD" state, and while git
doesn't care where you save the note about that state, in practice we
tend to just write the result to the file that is pointed at by
.git/HEAD, so that we can always see what the last committed state was.
OPTIONS
<tree> An existing tree object
-p <parent commit>
Each -p indicates the id of a parent commit object.
COMMIT INFORMATION
A commit encapsulates:
· all parent object ids
· author name, email and date
· committer name and email and the commit time.
While parent object ids are provided on the command line, author and
committer information is taken from the following environment
variables, if set:
GIT_AUTHOR_NAME
GIT_AUTHOR_EMAIL
GIT_AUTHOR_DATE
GIT_COMMITTER_NAME
GIT_COMMITTER_EMAIL
GIT_COMMITTER_DATE
EMAIL
(nb "<", ">" and "\n"s are stripped)
In case (some of) these environment variables are not set, the
information is taken from the configuration items user.name and
user.email, or, if not present, system user name and fully qualified
hostname.
A commit comment is read from stdin. If a changelog entry is not
provided via "<" redirection, "git-commit-tree" will just wait for
one to be entered and terminated with ^D.
DIAGNOSTICS
You don't exist. Go away!
The passwd(5) gecos field couldn't be read
Your parents must have hated you!
The password(5) gecos field is longer than a giant static
buffer.
Your sysadmin must hate you!
The password(5) name field is longer than a giant static buffer.
DISCUSSION
At the core level, git is character encoding agnostic.
· The pathnames recorded in the index and in the tree objects are
treated as uninterpreted sequences of non-NUL bytes. What readdir(2)
returns are what are recorded and compared with the data git keeps
track of, which in turn are expected to be what lstat(2) and
creat(2) accepts. There is no such thing as pathname encoding
translation.
· The contents of the blob objects are uninterpreted sequence of
bytes. There is no encoding translation at the core level.
· The commit log messages are uninterpreted sequence of non-NUL bytes.
Although we encourage that the commit log messages are encoded in
UTF-8, both the core and git Porcelain are designed not to force
UTF-8 on projects. If all participants of a particular project find
it more convenient to use legacy encodings, git does not forbid it.
However, there are a few things to keep in mind.
1. git-commit-tree (hence, git-commit which uses it) issues a warning
if the commit log message given to it does not look like a valid
UTF-8 string, unless you explicitly say your project uses a legacy
encoding. The way to say this is to have i18n.commitencoding in
.git/config file, like this:
[i18n]
commitencoding = ISO-8859-1
Commit objects created with the above setting record the value of
i18n.commitencoding in its encoding header. This is to help other
people who look at them later. Lack of this header implies that the
commit log message is encoded in UTF-8.
2. git-log, git-show and friends looks at the encoding header of a
commit object, and tries to re-code the log message into UTF-8
unless otherwise specified. You can specify the desired output
encoding with i18n.logoutputencoding in .git/config file, like this:
[i18n]
logoutputencoding = ISO-8859-1
If you do not have this configuration variable, the value of
i18n.commitencoding is used instead.
Note that we deliberately chose not to re-code the commit log
message when a commit is made to force UTF-8 at the commit object
level, because re-coding to UTF-8 is not necessarily a reversible
operation.
SEE ALSOgit-write-tree(1)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 git(7) suite
Git 1.5.5.2 10/21/2008 GIT-COMMIT-TREE(1)