From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: git@vger.kernel.org
Subject: [PATCH 2/6] Fix wording in push definition.
Date: Tue, 9 Oct 2007 23:01:05 +0200 [thread overview]
Message-ID: <20071009210105.GD31317@ins.uni-bonn.de> (raw)
In-Reply-To: <20071009205755.GB31317@ins.uni-bonn.de>
Make the definition of push in the glossary readable.
---
Documentation/glossary.txt | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
index d99fa19..5645177 100644
--- a/Documentation/glossary.txt
+++ b/Documentation/glossary.txt
@@ -301,8 +301,8 @@ This commit is referred to as a "merge commit", or sometimes just a
[[def_push]]push::
Pushing a <<def_branch,branch>> means to get the branch's
<<def_head_ref,head ref>> from a remote <<def_repository,repository>>,
- find out if it is an ancestor to the branch's local
- head ref is a direct, and in that case, putting all
+ find out if it is a direct ancestor to the branch's local
+ head ref, and in that case, putting all
objects, which are <<def_reachable,reachable>> from the local
head ref, and which are missing from the remote
repository, into the remote
--
1.5.3.3.g34c6d
next prev parent reply other threads:[~2007-10-09 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:57 [PATCH 0/6] Some small documentation fixes Ralf Wildenhues
2007-10-09 21:00 ` [PATCH 1/6] Fix some typos, punctuation, missing words, minor markup Ralf Wildenhues
2007-10-09 21:01 ` Ralf Wildenhues [this message]
2007-10-09 21:02 ` [PATCH 3/6] manual: Fix example finding commits referencing given content Ralf Wildenhues
2007-10-09 21:03 ` [PATCH 4/6] manual: add some markup Ralf Wildenhues
2007-10-09 21:03 ` [PATCH 5/6] manual: use 'URL' instead of 'url' Ralf Wildenhues
2007-10-09 21:05 ` [PATCH 0/6] manual: Fix or remove em dashes Ralf Wildenhues
2007-10-09 21:41 ` Thomas Adam
2007-10-09 21:52 ` Ralf Wildenhues
2007-10-09 22:02 ` Thomas Adam
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=20071009210105.GD31317@ins.uni-bonn.de \
--to=ralf.wildenhues@gmx.de \
--cc=git@vger.kernel.org \
/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).