summaryrefslogtreecommitdiffstats
path: root/man7/gittutorial.7
diff options
context:
space:
mode:
Diffstat (limited to 'man7/gittutorial.7')
-rw-r--r--man7/gittutorial.78
1 files changed, 4 insertions, 4 deletions
diff --git a/man7/gittutorial.7 b/man7/gittutorial.7
index 955b29619..08a5a5f6e 100644
--- a/man7/gittutorial.7
+++ b/man7/gittutorial.7
@@ -2,12 +2,12 @@
.\" Title: gittutorial
.\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\" Date: 2023-10-13
+.\" Date: 2023-10-18
.\" Manual: Git Manual
-.\" Source: Git 2.42.0.398.ga9ecda2788
+.\" Source: Git 2.42.0.411.g813d9a9188
.\" Language: English
.\"
-.TH "GITTUTORIAL" "7" "2023\-10\-13" "Git 2\&.42\&.0\&.398\&.ga9ecda" "Git Manual"
+.TH "GITTUTORIAL" "7" "2023\-10\-18" "Git 2\&.42\&.0\&.411\&.g813d9a" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -219,7 +219,7 @@ $ git commit \-a
.sp
which will automatically notice any modified (but not new) files, add them to the index, and commit, all in one step\&.
.sp
-A note on commit messages: Though not required, it\(cqs a good idea to begin the commit message with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description\&. The text up to the first blank line in a commit message is treated as the commit title, and that title is used throughout Git\&. For example, \fBgit-format-patch\fR(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body\&.
+A note on commit messages: Though not required, it\(cqs a good idea to begin the commit message with a single short (no more than 50 characters) line summarizing the change, followed by a blank line and then a more thorough description\&. The text up to the first blank line in a commit message is treated as the commit title, and that title is used throughout Git\&. For example, \fBgit-format-patch\fR(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body\&.
.SH "GIT TRACKS CONTENT NOT FILES"
.sp
Many revision control systems provide an \fBadd\fR command that tells the system to start tracking changes to a new file\&. Git\(cqs \fBadd\fR command does something simpler and more powerful: \fBgit add\fR is used both for new and newly modified files, and in both cases it takes a snapshot of the given files and stages that content in the index, ready for inclusion in the next commit\&.