Junio C Hamano <gits...@pobox.com> writes:
> second.pa...@gmail.com writes:
>
>> From: PAYRE NATHAN p1508475 <nathan.pa...@etu.univ-lyon1.fr>
>
> Should I assume that the name/address on the last Signed-off-by: we
> see below is what you want to be known as? As a part of school
> work, I'd imagine that Matthieu wants your work to be associated
> with the univ-lyon1.fr address, so perhaps you want to go the other
> way around?
Yes, I'd rather have contributions made with the identity
@etu.univ-lyon1.fr, and use the same identity for Signed-off-by: and
From:.
>> --path::
>> - 'git-config' will expand leading '{tilde}' to the value of
>> + 'git config' will expand leading '{tilde}' to the value of
>> '$HOME', and '{tilde}user' to the home directory for the
Didn't notice yesterday, but you still have forward quotes here and
backquotes right below. If you are to fix this paragraph, better fix all
issues at once.
>> specified user. This option has no effect when setting the
>> - value (but you can use 'git config bla {tilde}/' from the
>> - command line to let your shell do the expansion).
>> + value (but you can use `git config section.variable {tilde}/`
>
> Does this reference to {tilde} get expanded inside the `literal`
> mark-up? In the description for 'gitdir', we find this passage (in
> Documentation/config.txt):
>
> * If the pattern starts with `~/`, `~` will be substituted with the
> content of the environment variable `HOME`.
>
> So I'd expect `~` to be a safe way to get what you want, not `{tilde}`.
If I read correctly, the potential issue with ~ is that it's used for
subscript text (i.e. foo~bar~ in asciidoc is LaTeX's $foo_{bar}$). But ~
within a literal string should be safe, and at least we use it in many
places in our doc.
Cheers,
--
Matthieu Moy
https://matthieu-moy.fr/
