From: Ricardo Martincoski <ricardo.martincoski@gmail.com>
To: james.d.knight@live.com
Cc: ricardo.martincoski@datacom.com.br, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] utils/check-package: support ignore-indent flag for configurations
Date: Sun, 03 Sep 2023 13:13:28 -0300 [thread overview]
Message-ID: <64f4b0a8f236_809f62afed041072c192cd@xultri.mail> (raw)
In-Reply-To: SN4P221MB06823B0F7326D27ECD5E0FAEA0689@SN4P221MB0682.NAMP221.PROD.OUTLOOK.COM
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Hello,
Sorry the long delay.
On Sat, Apr 29, 2023 at 03:12 PM, James Knight wrote:
> from: James Knight <james.d.knight@live.com>
> date: Sat, Apr 29 02:12 PM -04:00 2023
> to: buildroot@buildroot.org
> cc: James Knight <james.d.knight@live.com>, Ricardo Martincoski <ricardo.martincoski@datacom.com.br>
> subject: [Buildroot] [PATCH 3/4] utils/check-package: support ignore-indent flag for configurations
>
> This commit provides the ability for configuration scripts to hint at
> ignoring linter checks for expected indentations. By adding the line to
> a configuration file:
>
> # noqa: ignore-indent
There is already support for comments in the form
# check-package Indent
to not run a CheckFunction named Indent for the next source code line
It seems to me that using 'check-package' in the special comment does
make sense because someone reading the source file, for instance a
Config.in file, can immediately know it is something related to the
check-package script, while a 'noqa' would need to be documented in the
manual.
Also, using 'check-package' in the comment would keep consistency with
code that already exists.
Finally, it seems to me more future-proof to keep the naming space of all
flags/options inside each CheckFunction, so I would suggest a comment in
the form:
# check-package Indent_ignore-menu-indent-below
that sets the flag named 'ignore-menu-indent-below' for the
CheckFunction named 'Indent' in the library that parses the type of file
that has the special comment, in the case of Config.in, lib_config.py.
Regards,
Ricardo
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-03 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230429181205.3620-1-james.d.knight@live.com>
2023-04-29 18:12 ` [Buildroot] [PATCH 1/4] utils/check-package: cleanup line reading James Knight
2023-08-26 20:09 ` Thomas Petazzoni via buildroot
2023-04-29 18:12 ` [Buildroot] [PATCH 2/4] utils/check-package: support a file-state instance for library types James Knight
2023-09-03 16:11 ` Ricardo Martincoski
2023-04-29 18:12 ` [Buildroot] [PATCH 3/4] utils/check-package: support ignore-indent flag for configurations James Knight
2023-09-03 16:13 ` Ricardo Martincoski [this message]
2023-04-29 18:12 ` [Buildroot] [PATCH 4/4] utils/check-package: utilize ignore-indent flag for special configs James Knight
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=64f4b0a8f236_809f62afed041072c192cd@xultri.mail \
--to=ricardo.martincoski@gmail.com \
--cc=buildroot@buildroot.org \
--cc=james.d.knight@live.com \
--cc=ricardo.martincoski@datacom.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.