Jean-Noël Avila <jn.avila@xxxxxxx> writes: > 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@xxxxxxx> > --- > Documentation/git-clone.txt | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Thanks. I've always wanted to do this, but it is a bit surprising that there is only this single instance? > 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>::
