All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Tomasz Warniełło" <tomasz.warniello@gmail.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts: kernel-doc: transform documentation into POD
Date: Mon, 03 Jan 2022 13:04:09 -0700	[thread overview]
Message-ID: <87bl0sziva.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220103183034.77ba8a8c@fuji.fritz.box>

Tomasz Warniełło <tomasz.warniello@gmail.com> writes:

> On Mon, 03 Jan 2022 11:04:53 +0200
> Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> In kernel, tabs are 8 characters.
>> 
>> See Documentation/process/coding-style.rst
>> 
>
> I am a heretic then.
>
> Except for the initial dogma, I understand and agree with the rationale
> in coding-style.rst.
>
> Only what if I have stared at the screen not for 20 hours, but for
> 40 hours? Now I want to have indentation even deeper, of 16 spaces.
> And how do I get this having 8 spaces here and there instead of tabs?
> The system begins to fall apart.
>
> The misleading statement is that tabs are 8 characters long. No. They
> are exactly 1 character long. And that's ASCII 9.

This is not particularly helpful.

I would like to get your work in, but need some cooperation to get
there.

Please:

 - Post your patch series as a single thread with a coherent cover
   letter.

 - Stick with current coding conventions

 - Avoid snide comments to reviewers.

Thanks,

jon

  reply	other threads:[~2022-01-03 20:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 22:55 [PATCH] scripts: kernel-doc: transform documentation into POD Tomasz Warniełło
2021-12-16 23:12 ` Jonathan Corbet
2021-12-17  9:43   ` Jani Nikula
2022-01-03  4:18   ` Tomasz Warniełło
2022-01-03  9:04     ` Jani Nikula
2022-01-03 17:30       ` Tomasz Warniełło
2022-01-03 20:04         ` Jonathan Corbet [this message]
2022-01-03 21:48           ` Tomasz Warniełło
2022-01-03 21:57             ` Jonathan Corbet
2022-01-03 23:56               ` Tomasz Warniełło
2022-01-03 20:40   ` Mauro Carvalho Chehab

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=87bl0sziva.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomasz.warniello@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.