From: "Jean-Noël Avila" <jn.avila@free.fr>
To: git@vger.kernel.org
Cc: "Jean-Noël Avila" <jn.avila@free.fr>
Subject: [PATCH 2/3] doc: remove non pure ASCII characters
Date: Thu, 12 Dec 2019 21:46:54 +0100 [thread overview]
Message-ID: <20191212204655.10425-2-jn.avila@free.fr> (raw)
In-Reply-To: <20191212204655.10425-1-jn.avila@free.fr>
Non ASCII characters may be handled by publishing chains, but right
now, nothing indicates the encoding of files. Moreover, non ASCII
source strings upset the localization toolchain.
Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
---
Documentation/git-clone.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
index 34011c2940..2e8babe671 100644
--- a/Documentation/git-clone.txt
+++ b/Documentation/git-clone.txt
@@ -262,9 +262,9 @@ or `--mirror` is given)
All submodules which are cloned will be shallow with a depth of 1.
--[no-]remote-submodules::
- All submodules which are cloned will use the status of the submodule’s
+ All submodules which are cloned will use the status of the submodule's
remote-tracking branch to update the submodule, rather than the
- superproject’s recorded SHA-1. Equivalent to passing `--remote` to
+ superproject's recorded SHA-1. Equivalent to passing `--remote` to
`git submodule update`.
--separate-git-dir=<git dir>::
--
2.24.0
next prev parent reply other threads:[~2019-12-12 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 20:46 [PATCH 1/3] doc: reword -B option of diff into something sensible Jean-Noël Avila
2019-12-12 20:46 ` Jean-Noël Avila [this message]
2019-12-13 19:53 ` [PATCH 2/3] doc: remove non pure ASCII characters Junio C Hamano
2019-12-13 21:37 ` Jean-Noël AVILA
2019-12-13 21:58 ` Junio C Hamano
2019-12-12 20:46 ` [PATCH 3/3] doc: indent multi-line items in list Jean-Noël Avila
2019-12-13 19:54 ` Junio C Hamano
2019-12-13 19:52 ` [PATCH 1/3] doc: reword -B option of diff into something sensible Junio C Hamano
2020-01-29 12:33 ` Jean-Noël Avila
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=20191212204655.10425-2-jn.avila@free.fr \
--to=jn.avila@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.