public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses•org>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: [PATCH 3/3] Docs: minor git-push copyediting
Date: Tue, 7 Feb 2006 03:22:48 +0000 (UTC)
Date: Sun Feb 5 19:42:27 2006 -0500	[thread overview]
Message-ID: <1139282428.ec02f402.2@fieldses.org> (raw)
In-Reply-To: <1139282428.ec02f402.1@fieldses.org>

Minor git-push copyediting

Signed-off-by: J. Bruce Fields <bfields@citi•umich.edu>

---

 Documentation/git-push.txt |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

a9a95125f25c8f70fe52ab0e30fe5ff6473d7679
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index ce909f5..5b89110 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -16,7 +16,7 @@ DESCRIPTION
 Updates remote refs using local refs, while sending objects
 necessary to complete the given refs.
 
-You can make "interesting" things to happen on the repository
+You can make interesting things happen to a repository
 every time you push into it, by setting up 'hooks' there.  See
 documentation for gitlink:git-receive-pack[1].
 
@@ -51,8 +51,8 @@ Some short-cut notations are also suppor
   in the source.
 
 \--all::
-	Instead of naming each ref to push, specifies all refs
-	to be pushed.
+	Instead of naming each ref to push, specifies that all
+	refs be pushed.
 
 \--tags::
 	All refs under `$GIT_DIR/refs/tags` are pushed, in
-- 
0.99.8b.g3480-dirty

      reply	other threads:[~2006-02-07  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  3:22 [PATCH 1/3] Docs: split up pull-fetch-param.txt J. Bruce Fields
2006-02-07  3:22 ` [PATCH 2/3] Docs: move git url and remotes text to separate sections J. Bruce Fields
2006-02-07  3:22   ` J. Bruce Fields [this message]

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=1139282428.ec02f402.2@fieldses.org \
    --to=bfields@fieldses$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=junkio@cox$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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