git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/6] user-manual: minor editing for conciseness

From
JFJ. Bruce Fields <bfields@citi.umich.edu>
Date
Aug 26, 2007, 16:16 UTC
Message-ID
<47129.6697076925$1188145040@news.gmane.org>
In-Reply-To
<11881450231606-git-send-email->
From: J. Bruce Fields <bfields@puzzle.fieldses.org>
Just cutting out a few unnecessary words.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
---
 Documentation/user-manual.txt |   10 +++-------
 1 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 0331bad..933177a 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -42,10 +42,9 @@ How to get a git repository
 It will be useful to have a git repository to experiment with as you
 read this manual.
 
-The best way to get one is by using the gitlink:git-clone[1] command
-to download a copy of an existing repository for a project that you
-are interested in.  If you don't already have a project in mind, here
-are some interesting examples:
+The best way to get one is by using the gitlink:git-clone[1] command to
+download a copy of an existing repository.  If you don't already have a
+project in mind, here are some interesting examples:
 
 ------------------------------------------------
 	# git itself (approx. 10MB download):
@@ -63,9 +62,6 @@ directory, you will see that it contains a copy of the project files,
 together with a special top-level directory named ".git", which
 contains all the information about the history of the project.
 
-In most of the following, examples will be taken from one of the two
-repositories above.
-
 [[how-to-check-out]]
 How to check out a different version of a project
 -------------------------------------------------
-- 
1.5.3.rc5.19.g0734d
Previous: J. Bruce FieldsNext: J. Bruce Fields
Message 2 of 7 in “user-manual: edit "ignoring files" for conciseness”
  1. 1/6 user-manual: edit "ignoring files" for concisenessJ. Bruce Fields, Aug 26, 2007
  2. 2/6 user-manual: minor editing for concisenessJ. Bruce Fields, Aug 26, 2007
  3. 3/6 user-manual: introduce the word "commit" earlierJ. Bruce Fields, Aug 26, 2007
  4. 4/6 user-manual: use pithier example commitJ. Bruce Fields, Aug 26, 2007
  5. 5/6 user-manual: fix incorrect header levelJ. Bruce Fields, Aug 26, 2007
  6. 6/6 Documentation/user-manual.txt: fix a few omissions of gitlink commands.J. Bruce Fields, Aug 26, 2007
  7. Johan HerlandAug 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.