git-commit-tree(1)
==================
-v0.1, May 2005
NAME
----
SYNOPSIS
--------
-'git-commit-tree' <tree> [-p <parent commit>]\ < changelog
+'git-commit-tree' <tree> [-p <parent commit>]\* < changelog
DESCRIPTION
-----------
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 `.git/HEAD`, so that we can
-always see what the last committed state was.
+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
-------
- committer name and email and the commit time.
If not provided, "git-commit-tree" uses your name, hostname and domain to
-provide author and committer info. This can be overridden using the
-following environment variables.
+provide author and committer info. This can be overridden by
+either `.git/config` file, or using the following environment variables.
GIT_AUTHOR_NAME
GIT_AUTHOR_EMAIL
(nb "<", ">" and "\n"s are stripped)
+In `.git/config` file, the following items are used for GIT_AUTHOR_NAME and
+GIT_AUTHOR_EMAIL:
+
+ [user]
+ name = "Your Name"
+ email = "your@email.address.xz"
+
A commit comment is read from stdin (max 999 chars). 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!::
Your sysadmin must hate you!::
The password(5) name field is longer than a giant static buffer.
+Discussion
+----------
+
+include::i18n.txt[]
+
See Also
--------
gitlink:git-write-tree[1]