public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 1/1] editorconfig: add consistent formatting rules for LTP
Date: Fri, 27 Mar 2026 16:29:52 +0100	[thread overview]
Message-ID: <20260327152952.GB1092845@pevik> (raw)
In-Reply-To: <69c66196.5d0a0220.2a94f1.b1f7@mx.google.com>

...
> > # Python and Perl: default to tabs (most test files use tabs, checkpatch.pl which we modify)
> > [*.{py,pl}]
> > indent_style = tab
> > indent_size = 8

> Not 100% sure about this.

> The Python test files in the tree (e.g. pm_sched_domain.py, pm_ilb_test.py)
> all use 4-space indentation, not tabs. The default for *.py should be
> indent_style = space / indent_size = 4. Perl (checkpatch.pl) does use tabs,
> so it should get its own section.

> Also kirk uses 4 tabs indentation. So I guess we need to invert the two rules
> at this point.

Would it work if kirk has it's own .editorconfig? I mean, it should have anyway,
but if it will be applied on it as a submodule.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  parent reply	other threads:[~2026-03-27 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 13:03 [LTP] [PATCH v2 1/1] editorconfig: add consistent formatting rules for LTP Jan Polensky
2026-03-27 10:53 ` Andrea Cervesato via ltp
2026-03-27 12:33   ` Petr Vorel
2026-03-27 13:39     ` Andrea Cervesato via ltp
2026-03-27 17:43       ` Petr Vorel
2026-03-27 18:25         ` Jan Polensky
2026-03-27 18:59           ` Petr Vorel
2026-03-27 15:29   ` Petr Vorel [this message]
2026-03-27 17:55     ` Jan Polensky
2026-03-27 18:25       ` Petr Vorel
2026-03-30  7:23     ` Andrea Cervesato via ltp
2026-03-31 19:59       ` Jan Polensky

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=20260327152952.GB1092845@pevik \
    --to=pvorel@suse.cz \
    --cc=andrea.cervesato@suse.com \
    --cc=ltp@lists.linux.it \
    /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