git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 05/10] Docs: git tag: Streamline a sentence.
Date: Mon, 28 Mar 2011 14:53:12 +0000	[thread overview]
Message-ID: <1301327622-8595-6-git-send-email-mfwitten@gmail.com> (raw)
In-Reply-To: <1301327622-8595-1-git-send-email-mfwitten@gmail.com>

Signed-off-by: Michael Witten <mfwitten@gmail.com>
---
 Documentation/git-tag.txt |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index b348c3d..9ec2715 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -211,8 +211,8 @@ $ git pull git://git..../proj.git master
 In such a case, you do not want to automatically follow the other
 person's tags.
 
-One important aspect of git is it is distributed, and being
-distributed largely means there is no inherent "upstream" or
+One important aspect of git is its distributed nature, which
+largely means there is no inherent "upstream" or
 "downstream" in the system.  On the face of it, the above
 example might seem to indicate that the tag namespace is owned
 by upper echelon of people and tags only flow downwards, but
-- 
1.7.4.18.g68fe8

  parent reply	other threads:[~2011-03-28 15:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 15:32 [PATCH 00/10] Docs: git tag Michael Witten
2011-03-28 14:35 ` [PATCH 01/10] Docs: git tag: Add `the' Michael Witten
2011-03-28 14:40 ` [PATCH 02/10] Docs: git tag: peoples back -> people's backs Michael Witten
2011-03-28 18:02   ` Eric Raible
2011-03-29  2:02     ` Michael Witten
2011-03-28 14:49 ` [PATCH 03/10] Docs: git tag: Revise a paragraph Michael Witten
2011-03-28 14:51 ` [PATCH 04/10] Docs: git tag: other's -> the other person's Michael Witten
2011-03-28 14:53 ` Michael Witten [this message]
2011-03-28 14:55 ` [PATCH 06/10] Docs: git tag: Add missing 'the' Michael Witten
2011-03-28 14:58 ` [PATCH 07/10] Docs: git tag: Use 'who' again Michael Witten
2011-03-28 14:59 ` [PATCH 08/10] Docs: git tag: Remove superfluous 'with' Michael Witten
2011-03-28 15:01 ` [PATCH 09/10] Docs: git tag: Use semicolon Michael Witten
2011-03-28 15:11 ` [PATCH 10/10] Docs: git tag: Rewrite discussion of GIT_COMMITTER_DATE Michael Witten
2011-03-28 18:04 ` [PATCH 00/10] Docs: git tag Junio C Hamano
2011-03-29  2:06   ` Michael Witten
2011-03-29  6:25   ` Michael J Gruber
2011-03-29 13:59     ` Michael Witten

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1301327622-8595-6-git-send-email-mfwitten@gmail.com \
    --to=mfwitten@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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. 
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 NNTP newsgroup(s).