Re: [PATCH] doc: fix unmatched code fences

From: Junio C Hamano <gitster@pobox.com>
Date: May 12, 2015, 18:45 UTC
Message-ID: <xmqqfv71zlaz.fsf@gitster.dls.corp.google.com>
In-Reply-To: <1431451400-1447-1-git-send-email-jn.avila@free.fr>

Jean-Noel Avila <jn.avila@free.fr> writes:

> This mismatch upsets the renderer on git-scm.com.

Thanks.

I do not think this is the first time AsciiDoc(or) rendering glitch was reported. GitHub folks, can you guys think of an automated way to spot these? Relying on site visitors to eyeball and hoping them to report is not an ideal approach.

Show 18 quoted lines

>
> Signed-off-by: Jean-Noel Avila <jn.avila@free.fr>
> ---
>  Documentation/gitcore-tutorial.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
> index 8475c07..36e9ab3 100644
> --- a/Documentation/gitcore-tutorial.txt
> +++ b/Documentation/gitcore-tutorial.txt
> @@ -259,7 +259,7 @@ index 557db03..263414f 100644
>  @@ -1 +1,2 @@
>   Hello World
>  +It's a new day for git
> -----
> +------------
>  
>  i.e. the diff of the change we caused by adding another line to `hello`.