FS/XFS testing framework
 help / color / mirror / Atom feed
From: Andrew Price <andyp@fedoraproject.org>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 1/2] xfstests: fix a typo in _require_block_device()
Date: Thu, 26 Feb 2015 11:41:10 +0000	[thread overview]
Message-ID: <54EF0656.6030206@fedoraproject.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1502261049520.25704@localhost.localdomain>


>>>> The change is fine - the reformating of the code is not. 8 space
>>>> tabs
>>>
>>> To be clear, do you mean 8 spaces or single tabs?
>>
>> Single tab, but tabs are the width of 8 spaces. Same as you'd use
>> for writing new kernel code.
>
> Even I was confused by that :) Just use tabs not spaces. Width of the
> tab is whatever your editor decides it is

Exactly :)

> so it's irrelevant :)

Well, unfortunately many use tabs for alignment as well as indentation 
so changing the width of a tab can make code look ugly where there are 
line continuations, aligned comments, etc. Using tabs for indentation 
and spaces for alignment is ideal, but tabs-for-alignment is so common 
that assuming tabs are always displayed 8 characters wide is often the 
pragmatic option.

Andy

      reply	other threads:[~2015-02-26 11:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  6:50 [PATCH 1/2] xfstests: fix a typo in _require_block_device() Zhaolei
2015-02-16  6:50 ` [PATCH 2/2] Fix warning of "Usage: _is_block_dev dev" Zhaolei
2015-02-18  5:37   ` Dave Chinner
2015-02-26  9:05     ` Zhao Lei
2015-02-26  9:30     ` Zhao Lei
2015-02-18  1:21 ` [PATCH 1/2] xfstests: fix a typo in _require_block_device() Dave Chinner
2015-02-18 10:21   ` Andrew Price
2015-02-18 22:02     ` Dave Chinner
2015-02-26  9:52       ` Lukáš Czerner
2015-02-26 11:41         ` Andrew Price [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=54EF0656.6030206@fedoraproject.org \
    --to=andyp@fedoraproject.org \
    --cc=fstests@vger.kernel.org \
    --cc=lczerner@redhat.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