A tiny documentation patch
- From
Štěpán Němec <stepnem@gmail.com>
- Date
- Aug 10, 2009, 14:44 UTC
- Message-ID
- <20090810144419.GB24183@headley>
Hello,
I noticed a few typos in the git-remote manpage, so I fixed the txt source file and here's the patch.
Best regards and thank you for Git!
Štěpán Němec
>From 65ae3e5cdb241aaaed96a7aeecffb6d305d0b07c Mon Sep 17 00:00:00 2001
From: =?utf-8?q?=C5=A0t=C4=9Bp=C3=A1n=20N=C4=9Bmec?= <stepnem@gmail.com> Date: Mon, 10 Aug 2009 16:29:08 +0200 Subject: [PATCH] Fix typos in git-remote.txt
--- Documentation/git-remote.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt index 9e2b4ea..0964cee 100644 --- a/Documentation/git-remote.txt +++ b/Documentation/git-remote.txt @@ -56,10 +56,10 @@ multiple branches without grabbing all branches. With `-m <master>` option, `$GIT_DIR/remotes/<name>/HEAD` is set up to point at remote's `<master>` branch. See also the set-head command. + -In mirror mode, enabled with `\--mirror`, the refs will not be stored +In mirror mode, enabled with `--mirror`, the refs will not be stored in the 'refs/remotes/' namespace, but in 'refs/heads/'. This option only makes sense in bare repositories. If a remote uses mirror -mode, furthermore, `git push` will always behave as if `\--mirror` +mode, furthermore, `git push` will always behave as if `--mirror` was passed. 'rename':: @@ -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]).
-- 1.6.3.3