git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* [PATCH] config.txt: fix a typo (backslash != backquote)
@ 2020-12-01 12:10 Štěpán Němec
  2020-12-01 19:29 ` Martin Ågren
  2020-12-01 21:31 ` Junio C Hamano
  0 siblings, 2 replies; 3+ messages in thread
From: Štěpán Němec @ 2020-12-01 12:10 UTC (permalink / raw)
  To: git

Signed-off-by: Štěpán Němec <stepnem@gmail.com>
---
 Documentation/config.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index bf706b950e..9700f6ebf9 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -64,7 +64,7 @@ The variable names are case-insensitive, allow only alphanumeric characters
 and `-`, and must start with an alphabetic character.
 
 A line that defines a value can be continued to the next line by
-ending it with a `\`; the backquote and the end-of-line are
+ending it with a `\`; the backslash and the end-of-line are
 stripped.  Leading whitespaces after 'name =', the remainder of the
 line after the first comment character '#' or ';', and trailing
 whitespaces of the line are discarded unless they are enclosed in
-- 
2.29.2


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] config.txt: fix a typo (backslash != backquote)
  2020-12-01 12:10 [PATCH] config.txt: fix a typo (backslash != backquote) Štěpán Němec
@ 2020-12-01 19:29 ` Martin Ågren
  2020-12-01 21:31 ` Junio C Hamano
  1 sibling, 0 replies; 3+ messages in thread
From: Martin Ågren @ 2020-12-01 19:29 UTC (permalink / raw)
  To: Štěpán Němec; +Cc: Git Mailing List

On Tue, 1 Dec 2020 at 13:12, Štěpán Němec <stepnem@gmail.com> wrote:
>  A line that defines a value can be continued to the next line by
> -ending it with a `\`; the backquote and the end-of-line are
> +ending it with a `\`; the backslash and the end-of-line are
>  stripped.  Leading whitespaces after 'name =', the remainder of the

Heh. The backslash is put inside backquotes for rendering as monospace,
so I can see how that happened. This change makes sense to me.

Martin

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] config.txt: fix a typo (backslash != backquote)
  2020-12-01 12:10 [PATCH] config.txt: fix a typo (backslash != backquote) Štěpán Němec
  2020-12-01 19:29 ` Martin Ågren
@ 2020-12-01 21:31 ` Junio C Hamano
  1 sibling, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2020-12-01 21:31 UTC (permalink / raw)
  To: Štěpán Němec; +Cc: git

Štěpán Němec <stepnem@gmail.com> writes:

> Signed-off-by: Štěpán Němec <stepnem@gmail.com>
> ---
>  Documentation/config.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks for spotting an ancient typo that is more than 5 years old.

>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index bf706b950e..9700f6ebf9 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -64,7 +64,7 @@ The variable names are case-insensitive, allow only alphanumeric characters
>  and `-`, and must start with an alphabetic character.
>  
>  A line that defines a value can be continued to the next line by
> -ending it with a `\`; the backquote and the end-of-line are
> +ending it with a `\`; the backslash and the end-of-line are
>  stripped.  Leading whitespaces after 'name =', the remainder of the
>  line after the first comment character '#' or ';', and trailing
>  whitespaces of the line are discarded unless they are enclosed in

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-12-01 21:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-01 12:10 [PATCH] config.txt: fix a typo (backslash != backquote) Štěpán Němec
2020-12-01 19:29 ` Martin Ågren
2020-12-01 21:31 ` Junio C Hamano

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).