GIT\-COMMIT\-TREESection: Git Manual (1)
Index Return to Main Contents
NAMEgit-commit-tree - Create a new commit object
SYNOPSISgit-commit-tree <tree> [-p <parent commit>]* < changelog
DESCRIPTIONThis 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.
- An existing tree object
-p <parent commit>
- Each -p indicates the id of a parent commit object.
COMMIT INFORMATIONA commit encapsulates:
- *all parent object ids
- *author name, email and date
- *committer name and email and the commit time.
GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL GIT_AUTHOR_DATE GIT_COMMITTER_NAME GIT_COMMITTER_EMAIL GIT_COMMITTER_DATE EMAIL
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.
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.
DISCUSSIONAt 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.
1.git-commit-tree (hence, git-commit which uses it) issues an 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:
.ft C [i18n] commitencoding = ISO-8859-1 .ft
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:
.ft C [i18n] logoutputencoding = ISO-8859-1 .ft
AUTHORWritten by Linus Torvalds <email@example.com>
DOCUMENTATIONDocumentation by David Greaves, Junio C Hamano and the git-list <firstname.lastname@example.org>.
GITPart of the git(7) suite
- COMMIT INFORMATION
- SEE ALSO