[LTP] [PATCH v2 1/1] editorconfig: add consistent formatting rules for LTP

[Petr Vorel]

...
> > 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
> Hi Petr,

> In upstream LTP, kirk is actually included as a git submodule at
> `tools/kirk` (see `.gitmodules`), so having kirk carry its own
> `.editorconfig` is a natural fit.

> EditorConfig is directory-hierarchical: editors look for `.editorconfig`
> files from the file’s directory upwards, and the closest matching
> settings override parent ones. If kirk’s `.editorconfig` sets `root =
> true`, the lookup stops at the submodule root, so LTP’s top-level rules
> won’t affect files inside `tools/kirk`.

+1 (this was my question), thanks for info. Hopefully this is widely supported
feature (I haven't found it on the wiki).

> Alternatively, if one prefer a single policy file, one could keep
> everything in LTP’s top-level `.editorconfig` and add a dedicated
> override section like `[tools/kirk/**]`.

Thanks for info. That would not work because the primary development is in kirk
repo, let's have the config there.

Kind regards,
Petr

> Kind regards,
> Jan