public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Daniel Xu <dxu@dxuuu.xyz>, linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: Re: [PATCH] btrfs-progs: Add basic .editorconfig
Date: Tue, 28 Jul 2020 09:57:16 +0800	[thread overview]
Message-ID: <349343e3-8687-d217-66f8-59d50e8a8ced@gmx.com> (raw)
In-Reply-To: <85567980-5c9f-99a9-80e3-89e6418ed86f@gmx.com>


[-- Attachment #1.1: Type: text/plain, Size: 1826 bytes --]



On 2020/7/28 上午9:50, Qu Wenruo wrote:
> 
> 
> On 2020/7/28 上午9:24, Daniel Xu wrote:
>> Not all contributors work on projects that use linux kernel coding
>> style. This commit adds a basic editorconfig [0] to assist contributors
>> with managing configuration.
>>
>> [0]: https://editorconfig.org/
> 
> I like the idea of the generic style file.
> It's just one single file for all editors.
> 
> Although most btrfs developers I know use vim, and it's not supported
> natively, it shouldn't be a big problem, a plugin would handle it
> without problem.
> 
>>
>> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
> 
> Reviewed-by: Qu Wenruo <wqu@suse.com>
> 
> But a small nitpick inlined below.
> 
>> ---
>>  .editorconfig | 10 ++++++++++
>>  .gitignore    |  1 +
>>  2 files changed, 11 insertions(+)
>>  create mode 100644 .editorconfig
>>
>> diff --git a/.editorconfig b/.editorconfig
>> new file mode 100644
>> index 00000000..2829cfbe
>> --- /dev/null
>> +++ b/.editorconfig
>> @@ -0,0 +1,10 @@
>> +[*]
>> +end_of_line = lf
>> +insert_final_newline = true
>> +trim_trailing_whitespace = true
>> +charset = utf-8
>> +indent_style = space

Wait for a minute, does that mean, we use space as indent?
IIRC kernel code style goes tab if possible?

Thanks,
Qu

>> +indent_size = 8
>> +
>> +[*.py]
>> +indent_size = 4
>> diff --git a/.gitignore b/.gitignore
>> index aadf9ae7..1c70ec94 100644
>> --- a/.gitignore
>> +++ b/.gitignore
>> @@ -65,6 +65,7 @@
>>  /cscope.in.out
>>  /cscope.po.out
>>  .*
>> +!.editorconfig
> 
> You can force add that file and git should handle it without problem,
> and later modification would also be traced by git.
> 
> Thanks,
> Qu
> 
>>
>>  /Documentation/Makefile
>>  /Documentation/*.html
>> --
>> 2.27.0
>>
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-28  1:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  1:24 [PATCH] btrfs-progs: Add basic .editorconfig Daniel Xu
2020-07-28  1:50 ` Qu Wenruo
2020-07-28  1:57   ` Qu Wenruo [this message]
2020-07-28  1:57     ` Daniel Xu

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=349343e3-8687-d217-66f8-59d50e8a8ced@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=dxu@dxuuu.xyz \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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