jm...@redhat.com writes:
> From: Jakob Meng
>
> Wildcard sections [*] and [**] are unsafe because properties cannot be
> applied safely to any filetype in general. For example, IDEs like
> Visual Studio Code and KDevelop store configuration files in subfolders
> like .vscode or .kdev4.
On Mon, Oct 30, 2023 at 09:54:58AM +0100, Jakob Meng wrote:
> Hi Aaron,
>
> first and foremost: I am fully committed to make our OVS community more
> inclusive. Replacing terminology that promotes racial and cultural bias is
> one of many (!) steps in achieving that. For the objective there is
Hi Aaron,
first and foremost: I am fully committed to make our OVS community more
inclusive. Replacing terminology that promotes racial and cultural bias is one
of many (!) steps in achieving that. For the objective there is a broad
consensus, on the practical implementation not so much, it
Hi Jakob,
Just a comment about the use of 'whitespace' in the commit message.
There is an effort to try and use more inclusive language, so it might
be good to use empty-space or blank-space in the commit message. I know
that it is an editor config property, so not much to do about
, Oct 27, 2023 at 14:10:
From: Jakob Meng
Wildcard sections [*] and [**] are unsafe because properties cannot be
applied safely to any filetype in general. For example, IDEs like
Visual Studio Code and KDevelop store configuration files in subfolders
like .vscode or .kdev4. Properties from
On 27 Oct 2023, at 14:10, jm...@redhat.com wrote:
> From: Jakob Meng
>
> Wildcard sections [*] and [**] are unsafe because properties cannot be
> applied safely to any filetype in general. For example, IDEs like
> Visual Studio Code and KDevelop store configuration files in subfolders
> like
From: Jakob Meng
Wildcard sections [*] and [**] are unsafe because properties cannot be
applied safely to any filetype in general. For example, IDEs like
Visual Studio Code and KDevelop store configuration files in subfolders
like .vscode or .kdev4. Properties from wildcard sections also apply
