From: "Štěpán Němec" <stepan.nemec@gmail.com>
To: git@vger.kernel.org
Cc: trast@student.ethz.ch
Subject: [PATCH] Fix typos in git-remote.txt and git-symbolic-ref.txt
Date: Tue, 11 Aug 2009 02:52:07 +0200 [thread overview]
Message-ID: <20090811005207.GE24183@headley> (raw)
Signed-off-by: Štěpán Němec <stepnem@gmail.com>
---
I apologize for the previous mail.
Thank you for clarification and guidance.
I did look at some of the other documentation files (and now also grepped
the whole directory for `--' and `\--' occurences), but wasn't able to see
any rule or consistence in the usage. Whether it is an indication of
real inconsistence or just another example of my ignorance I do not know
(not now, at least).
The stray backslashes were fixed by setting ASCIIDOC8, thanks again.
Štěpán Němec
Documentation/git-remote.txt | 4 ++--
Documentation/git-symbolic-ref.txt | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index 9e2b4ea..82a3d29 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -114,14 +114,14 @@ These stale branches have already been removed from the remote repository
referenced by <name>, but are still locally available in
"remotes/<name>".
+
-With `--dry-run` option, report what branches will be pruned, but do no
+With `--dry-run` option, report what branches will be pruned, but do not
actually prune them.
'update'::
Fetch updates for a named set of remotes in the repository as defined by
remotes.<group>. If a named group is not specified on the command line,
-the configuration parameter remotes.default will get used; if
+the configuration parameter remotes.default will be used; if
remotes.default is not defined, all remotes which do not have the
configuration parameter remote.<name>.skipDefaultUpdate set to true will
be updated. (See linkgit:git-config[1]).
diff --git a/Documentation/git-symbolic-ref.txt b/Documentation/git-symbolic-ref.txt
index 210fde0..6392538 100644
--- a/Documentation/git-symbolic-ref.txt
+++ b/Documentation/git-symbolic-ref.txt
@@ -14,9 +14,9 @@ DESCRIPTION
Given one argument, reads which branch head the given symbolic
ref refers to and outputs its path, relative to the `.git/`
directory. Typically you would give `HEAD` as the <name>
-argument to see on which branch your working tree is on.
+argument to see which branch your working tree is on.
-Give two arguments, create or update a symbolic ref <name> to
+Given two arguments, creates or updates a symbolic ref <name> to
point at the given branch <ref>.
A symbolic ref is a regular file that stores a string that
--
1.6.3.3
next reply other threads:[~2009-08-11 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 0:52 Štěpán Němec [this message]
2009-08-11 5:13 ` [PATCH] Fix typos in git-remote.txt and git-symbolic-ref.txt Junio C Hamano
2009-08-11 7:09 ` Thomas Rast
2009-08-12 0:26 ` Wesley J. Landaker
2009-08-12 13:40 ` Thomas Rast
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=20090811005207.GE24183@headley \
--to=stepan.nemec@gmail.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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