git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/5] Documentation: turn middle-of-line tabs into spaces
Date: Thu, 07 Mar 2019 09:29:46 +0900	[thread overview]
Message-ID: <xmqqr2bjo7b9.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <4348f7b1b661181b90bf25f43c07529fa9757422.1551853194.git.martin.agren@gmail.com> ("Martin Ågren"'s message of "Wed, 6 Mar 2019 07:30:18 +0100")

Martin Ågren <martin.agren@gmail.com> writes:

> These tabs happen to appear in columns where they don't stand out too
> much, so the diff here is non-obvious. Some of these are rendered
> differently by AsciiDoc and Asciidoctor (although the difference might
> be invisible!), which is how I found a few of them. The remainder were
> found using `git grep "[a-zA-Z.,)]$TAB[a-zA-Z]"`.

Thanks.  This was a fun-to-read patch.

> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
> index b9fd3770a6..0b057cbb10 100644
> --- a/Documentation/git-ls-remote.txt
> +++ b/Documentation/git-ls-remote.txt
> @@ -31,7 +31,7 @@ OPTIONS
>  	displayed.
>  
>  --refs::
> -	Do not show peeled tags or pseudorefs like HEAD	in the output.
> +	Do not show peeled tags or pseudorefs like `HEAD` in the output.

The quoting fix here is also good.

      reply	other threads:[~2019-03-07  0:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  6:30 [PATCH 0/5] fixing a few Asciidoc/tor differences Martin Ågren
2019-03-06  6:30 ` [PATCH 1/5] config/diff.txt: drop spurious backtick Martin Ågren
2019-03-06  6:30 ` [PATCH 2/5] config/fsck.txt: avoid starting line with dash Martin Ågren
2019-03-06  6:30 ` [PATCH 3/5] git.txt: remove empty line before list continuation Martin Ågren
2019-03-06  6:30 ` [PATCH 4/5] git-svn.txt: drop escaping '\' that ends up being rendered Martin Ågren
2019-03-06  6:30 ` [PATCH 5/5] Documentation: turn middle-of-line tabs into spaces Martin Ågren
2019-03-07  0:29   ` Junio C Hamano [this message]

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=xmqqr2bjo7b9.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=martin.agren@gmail.com \
    /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 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 NNTP newsgroup(s).