2005-05-11 01:32:30 +04:00
|
|
|
git-commit-tree(1)
|
|
|
|
==================
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
2007-01-19 02:53:37 +03:00
|
|
|
git-commit-tree - Create a new commit object
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2011-07-02 06:38:26 +04:00
|
|
|
[verse]
|
2010-10-08 21:31:17 +04:00
|
|
|
'git commit-tree' <tree> [(-p <parent commit>)...] < changelog
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2007-01-18 00:03:29 +03:00
|
|
|
This is usually not what an end user wants to run directly. See
|
2007-12-29 09:20:38 +03:00
|
|
|
linkgit:git-commit[1] instead.
|
2007-01-18 00:03:29 +03:00
|
|
|
|
2005-05-11 01:32:30 +04:00
|
|
|
Creates a new commit object based on the provided tree object and
|
2008-08-08 11:52:55 +04:00
|
|
|
emits the new commit object id on stdout.
|
2005-05-11 01:32:30 +04:00
|
|
|
|
2008-08-08 11:52:55 +04:00
|
|
|
A commit object may have any number of parents. With exactly one
|
|
|
|
parent, it is an ordinary commit. Having more than one parent makes
|
|
|
|
the commit a merge between several lines of history. Initial (root)
|
|
|
|
commits have no parents.
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
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
|
2005-11-17 08:32:44 +03:00
|
|
|
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.
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
-------
|
|
|
|
<tree>::
|
|
|
|
An existing tree object
|
|
|
|
|
|
|
|
-p <parent commit>::
|
2005-10-06 02:08:26 +04:00
|
|
|
Each '-p' indicates the id of a parent commit object.
|
2007-06-07 11:04:01 +04:00
|
|
|
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
Commit Information
|
|
|
|
------------------
|
|
|
|
|
|
|
|
A commit encapsulates:
|
|
|
|
|
|
|
|
- all parent object ids
|
|
|
|
- author name, email and date
|
|
|
|
- committer name and email and the commit time.
|
|
|
|
|
2007-08-18 00:13:36 +04:00
|
|
|
While parent object ids are provided on the command line, author and
|
2007-08-24 04:44:13 +04:00
|
|
|
committer information is taken from the following environment variables,
|
2007-08-18 00:13:36 +04:00
|
|
|
if set:
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
GIT_AUTHOR_NAME
|
|
|
|
GIT_AUTHOR_EMAIL
|
|
|
|
GIT_AUTHOR_DATE
|
|
|
|
GIT_COMMITTER_NAME
|
|
|
|
GIT_COMMITTER_EMAIL
|
2007-04-29 05:40:12 +04:00
|
|
|
GIT_COMMITTER_DATE
|
2007-04-29 05:40:28 +04:00
|
|
|
EMAIL
|
2005-05-11 01:32:30 +04:00
|
|
|
|
2005-10-03 21:16:30 +04:00
|
|
|
(nb "<", ">" and "\n"s are stripped)
|
2005-05-11 01:32:30 +04:00
|
|
|
|
2007-08-18 00:13:36 +04:00
|
|
|
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
|
ident: check /etc/mailname if email is unknown
Before falling back to gethostname(), check /etc/mailname if
GIT_AUTHOR_EMAIL is not set in the environment or through config
files. Only fall back if /etc/mailname cannot be opened or read.
The /etc/mailname convention comes from Debian policy section 11.6
("mail transport, delivery and user agents"), though maybe it could be
useful sometimes on other machines, too. The lack of this support was
noticed by various people in different ways:
- Ian observed that git was choosing the address
'ian@anarres.relativity.greenend.org.uk' rather than
'ian@davenant.greenend.org.uk' as it should have done.
- Jonathan noticed that operations like "git commit" were needlessly
slow when using a resolver that was slow to handle reverse DNS
lookups.
Alas, after this patch, if /etc/mailname is set up and the [user] name
and email configuration aren't, the committer email will not provide a
charming reminder of which machine commits were made on any more. But
I think it's worth it.
Mechanics: the functionality of reading mailname goes in its own
function, so people who care about other distros can easily add an
implementation to a similar location without making copy_email() too
long and losing clarity. While at it, we split out the fallback
default logic that does gethostname(), too (rearranging it a little
and adding a check for errors from gethostname while at it).
Based on a patch by Gerrit Pape <pape@smarden.org>.
Requested-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Improved-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-10-03 10:16:33 +04:00
|
|
|
present, system user name and the hostname used for outgoing mail (taken
|
|
|
|
from `/etc/mailname` and falling back to the fully qualified hostname when
|
|
|
|
that file does not exist).
|
2005-10-30 01:32:56 +04:00
|
|
|
|
2007-07-15 09:56:47 +04:00
|
|
|
A commit comment is read from stdin. If a changelog
|
2010-01-10 02:33:00 +03:00
|
|
|
entry is not provided via "<" redirection, 'git commit-tree' will just wait
|
2005-10-03 21:16:30 +04:00
|
|
|
for one to be entered and terminated with ^D.
|
2005-05-11 01:32:30 +04:00
|
|
|
|
2009-12-03 02:49:19 +03:00
|
|
|
include::date-formats.txt[]
|
2005-10-30 01:32:56 +04:00
|
|
|
|
2005-05-11 01:32:38 +04:00
|
|
|
Diagnostics
|
|
|
|
-----------
|
|
|
|
You don't exist. Go away!::
|
|
|
|
The passwd(5) gecos field couldn't be read
|
2005-07-15 04:57:53 +04:00
|
|
|
Your parents must have hated you!::
|
2008-09-03 12:50:43 +04:00
|
|
|
The passwd(5) gecos field is longer than a giant static buffer.
|
2005-07-15 04:57:53 +04:00
|
|
|
Your sysadmin must hate you!::
|
2008-09-03 12:50:43 +04:00
|
|
|
The passwd(5) name field is longer than a giant static buffer.
|
2005-05-11 01:32:38 +04:00
|
|
|
|
2006-12-30 13:22:38 +03:00
|
|
|
Discussion
|
|
|
|
----------
|
|
|
|
|
|
|
|
include::i18n.txt[]
|
|
|
|
|
ident: check /etc/mailname if email is unknown
Before falling back to gethostname(), check /etc/mailname if
GIT_AUTHOR_EMAIL is not set in the environment or through config
files. Only fall back if /etc/mailname cannot be opened or read.
The /etc/mailname convention comes from Debian policy section 11.6
("mail transport, delivery and user agents"), though maybe it could be
useful sometimes on other machines, too. The lack of this support was
noticed by various people in different ways:
- Ian observed that git was choosing the address
'ian@anarres.relativity.greenend.org.uk' rather than
'ian@davenant.greenend.org.uk' as it should have done.
- Jonathan noticed that operations like "git commit" were needlessly
slow when using a resolver that was slow to handle reverse DNS
lookups.
Alas, after this patch, if /etc/mailname is set up and the [user] name
and email configuration aren't, the committer email will not provide a
charming reminder of which machine commits were made on any more. But
I think it's worth it.
Mechanics: the functionality of reading mailname goes in its own
function, so people who care about other distros can easily add an
implementation to a similar location without making copy_email() too
long and losing clarity. While at it, we split out the fallback
default logic that does gethostname(), too (rearranging it a little
and adding a check for errors from gethostname while at it).
Based on a patch by Gerrit Pape <pape@smarden.org>.
Requested-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Improved-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-10-03 10:16:33 +04:00
|
|
|
FILES
|
|
|
|
-----
|
|
|
|
/etc/mailname
|
|
|
|
|
2008-05-29 03:55:27 +04:00
|
|
|
SEE ALSO
|
2005-05-11 01:32:38 +04:00
|
|
|
--------
|
2007-12-29 09:20:38 +03:00
|
|
|
linkgit:git-write-tree[1]
|
2005-05-11 01:32:30 +04:00
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
2008-06-06 11:07:32 +04:00
|
|
|
Part of the linkgit:git[1] suite
|