From: "J. Bruce Fields" <bfields@citi.umich.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, "J. Bruce Fields" <bfields@citi.umich.edu>
Subject: [PATCH 3/6] user-manual: introduce the word "commit" earlier
Date: Sun, 26 Aug 2007 12:16:59 -0400 [thread overview]
Message-ID: <10992.4252414659$1188145046@news.gmane.org> (raw)
Message-ID: <a2ef9d633f67edc227b00209d5b72ec388388877.1188139206.git.bfields@citi.umich.edu> (raw)
In-Reply-To: <11881450231010-git-send-email->
In-Reply-To: <464a8a7a15fc70efbcf56c4569f0f7275a9c76fe.1188139206.git.bfields@citi.umich.edu>
From: J. Bruce Fields <bfields@citi.umich.edu>
Use the word "commit" as a synonym for "version" from the start.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
---
Documentation/user-manual.txt | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 933177a..6d35a1f 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -66,14 +66,14 @@ contains all the information about the history of the project.
How to check out a different version of a project
-------------------------------------------------
-Git is best thought of as a tool for storing the history of a
-collection of files. It stores the history as a compressed
-collection of interrelated snapshots (versions) of the project's
-contents.
+Git is best thought of as a tool for storing the history of a collection
+of files. It stores the history as a compressed collection of
+interrelated snapshots of the project's contents. In git each such
+version is called a <<def_commit,commit>>.
A single git repository may contain multiple branches. It keeps track
of them by keeping a list of <<def_head,heads>> which reference the
-latest version on each branch; the gitlink:git-branch[1] command shows
+latest commit on each branch; the gitlink:git-branch[1] command shows
you the list of branch heads:
------------------------------------------------
--
1.5.3.rc5.19.g0734d
next prev parent reply other threads:[~2007-08-26 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11881450221019-git-send-email->
[not found] ` <464a8a7a15fc70efbcf56c4569f0f7275a9c76fe.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16 ` [PATCH 1/6] user-manual: edit "ignoring files" for conciseness J. Bruce Fields
[not found] ` <a5f90f31302eb47cb1aa2f12447376ff9332abef.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16 ` [PATCH 2/6] user-manual: minor editing " J. Bruce Fields
[not found] ` <a2ef9d633f67edc227b00209d5b72ec388388877.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16 ` J. Bruce Fields [this message]
[not found] ` <e2618ff42716dd7cbc7a353670f46f357c5fb4c5.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:17 ` [PATCH 4/6] user-manual: use pithier example commit J. Bruce Fields
[not found] ` <d5821de2e29a3a207a2c5188f73b7d1f6d52fc34.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:17 ` [PATCH 5/6] user-manual: fix incorrect header level J. Bruce Fields
[not found] ` <a115daff12d8d26975ff15a4278a212df2c8c70b.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:17 ` [PATCH 6/6] Documentation/user-manual.txt: fix a few omissions of gitlink commands J. Bruce Fields
[not found] ` <11881450231606-git-send-email->
[not found] ` <11881450231010-git-send-email->
[not found] ` <11881450233251-git-send-email->
[not found] ` <11881450231946-git-send-email->
2007-08-26 19:57 ` [PATCH 1/6] user-manual: edit "ignoring files" for conciseness Johan Herland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='10992.4252414659$1188145046@news.gmane.org' \
--to=bfields@citi.umich.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).