All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Thymo van Beers <thymovanbeers@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs: kernel-parameters.txt: Fix whitespace
Date: Fri, 27 Apr 2018 16:50:59 -0600	[thread overview]
Message-ID: <20180427165059.3936a6e3@lwn.net> (raw)
In-Reply-To: <20180418185136.GA27678@thinkpad>

On Wed, 18 Apr 2018 20:51:39 +0200
Thymo van Beers <thymovanbeers@gmail.com> wrote:

> Some lines used spaces instead of tabs at line start.
> This can cause mangled lines in editors due to inconsistency.
> 
> Replace spaces for tabs where appropriate.

Applied, thanks.

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Thymo van Beers <thymovanbeers@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] docs: kernel-parameters.txt: Fix whitespace
Date: Fri, 27 Apr 2018 16:50:59 -0600	[thread overview]
Message-ID: <20180427165059.3936a6e3@lwn.net> (raw)
In-Reply-To: <20180418185136.GA27678@thinkpad>

On Wed, 18 Apr 2018 20:51:39 +0200
Thymo van Beers <thymovanbeers@gmail.com> wrote:

> Some lines used spaces instead of tabs at line start.
> This can cause mangled lines in editors due to inconsistency.
> 
> Replace spaces for tabs where appropriate.

Applied, thanks.

jon

  parent reply	other threads:[~2018-04-27 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 18:51 [PATCH v3] docs: kernel-parameters.txt: Fix whitespace Thymo van Beers
2018-04-18 18:51 ` Thymo van Beers
2018-04-18 20:09 ` Randy Dunlap
2018-04-18 20:09   ` Randy Dunlap
2018-04-27 22:50 ` Jonathan Corbet [this message]
2018-04-27 22:50   ` Jonathan Corbet

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=20180427165059.3936a6e3@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thymovanbeers@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.