From: Thomas Rast <trast@student.ethz.ch>
To: "Štěpán Němec" <stepnem@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: A tiny documentation patch
Date: Mon, 10 Aug 2009 16:59:27 +0200 [thread overview]
Message-ID: <200908101659.28291.trast@student.ethz.ch> (raw)
In-Reply-To: <20090810144419.GB24183@headley>
Štěpán Němec wrote:
> here's the patch.
Please read Documentation/SubmittingPatches. In particular, you
should send your patch inline (git-send-email can help) and add a
Signed-off-by.
> I noticed a few typos in the git-remote manpage
[...]
> diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
[...]
> -In mirror mode, enabled with `\--mirror`, the refs will not be stored
> +In mirror mode, enabled with `--mirror`, the refs will not be stored
[...]
> -mode, furthermore, `git push` will always behave as if `\--mirror`
> +mode, furthermore, `git push` will always behave as if `--mirror`
While I'm not sure how far back you'd have to go to find an asciidoc
that does need this escaping, it's definitely *not* a typo. In some
instances, -- turns into em dashes.
If you are seeing stray backslashes in the output (I don't), I suspect
you are either running asciidoc 8.x but forgot to set ASCIIDOC8, or
8.4.1+ and are missing the patch 71c020c (Disable asciidoc 8.4.1+
semantics for `{plus}` and friends, 2009-07-25).
> -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.
Ok.
> 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
Ok.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-08-10 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 14:44 A tiny documentation patch Štěpán Němec
2009-08-10 14:59 ` Thomas Rast [this message]
2009-08-11 8:01 ` Michael J Gruber
2009-08-12 2:55 ` Junio C Hamano
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=200908101659.28291.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=stepnem@gmail.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).