diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2007-08-06 06:42:24 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2007-08-06 06:42:24 +0000 |
| commit | bd2b4bbb74c94d27ad61268c94f4cbde040b2fec (patch) | |
| tree | 3d42fadfe9f24014f026a07195f55ed6c841e172 /git-commit.txt | |
| parent | 4cd1c0eeb17ef53283e40f2f1cc8bc952422b3c7 (diff) | |
| download | git-htmldocs-bd2b4bbb74c94d27ad61268c94f4cbde040b2fec.tar.gz | |
Autogenerated HTML docs for v1.5.3-rc4-16-ga76c
Diffstat (limited to 'git-commit.txt')
| -rw-r--r-- | git-commit.txt | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/git-commit.txt b/git-commit.txt index 627994eb9..63599d382 100644 --- a/git-commit.txt +++ b/git-commit.txt @@ -15,26 +15,26 @@ SYNOPSIS DESCRIPTION ----------- -Use 'git commit' when you want to record your changes into the repository -along with a log message describing what the commit is about. All changes -to be committed must be explicitly identified using one of the following -methods: +Use 'git commit' to store the current contents of the index in a new +commit along with a log message describing the changes you have made. +The content to be added can be specified in several ways: 1. by using gitlink:git-add[1] to incrementally "add" changes to the - next commit before using the 'commit' command (Note: even modified + index before using the 'commit' command (Note: even modified files must be "added"); -2. by using gitlink:git-rm[1] to identify content removal for the next - commit, again before using the 'commit' command; +2. by using gitlink:git-rm[1] to remove files from the working tree + and the index, again before using the 'commit' command; -3. by directly listing files containing changes to be committed as arguments - to the 'commit' command, in which cases only those files alone will be - considered for the commit; +3. by listing files as arguments to the 'commit' command, in which + case the commit will ignore changes staged in the index, and instead + record the current content of the listed files; -4. by using the -a switch with the 'commit' command to automatically "add" - changes from all known files i.e. files that have already been committed - before, and to automatically "rm" files that have been - removed from the working tree, and perform the actual commit. +4. by using the -a switch with the 'commit' command to automatically + "add" changes from all known files (i.e. all files that are already + listed in the index) and to automatically "rm" files in the index + that have been removed from the working tree, and then perform the + actual commit; 5. by using the --interactive switch with the 'commit' command to decide one by one which files should be part of the commit, before finalizing the |