git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "J. Bruce Fields" <bfields@citi.umich.edu>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org,
	"J. Bruce Fields" <bfields@puzzle.fieldses.org>,
	"J. Bruce Fields" <bfields@citi.umich.edu>
Subject: [PATCH 2/6] user-manual: minor editing for conciseness
Date: Sun, 26 Aug 2007 12:16:58 -0400	[thread overview]
Message-ID: <47129.6697076925$1188145040@news.gmane.org> (raw)
Message-ID: <a5f90f31302eb47cb1aa2f12447376ff9332abef.1188139206.git.bfields@citi.umich.edu> (raw)
In-Reply-To: <11881450231606-git-send-email->
In-Reply-To: <464a8a7a15fc70efbcf56c4569f0f7275a9c76fe.1188139206.git.bfields@citi.umich.edu>

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

  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     ` J. Bruce Fields [this message]
     [not found]   ` <a2ef9d633f67edc227b00209d5b72ec388388877.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16     ` [PATCH 3/6] user-manual: introduce the word "commit" earlier J. Bruce Fields
     [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='47129.6697076925$1188145040@news.gmane.org' \
    --to=bfields@citi.umich.edu \
    --cc=bfields@puzzle.fieldses.org \
    --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).