public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Patrick O'Neill <poneill@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-4341] check_GNU_style.py: Skip .md square bracket linting Date: Fri, 29 Sep 2023 21:13:38 +0000 (GMT) [thread overview] Message-ID: <20230929211338.BB3433858D32@sourceware.org> (raw) https://gcc.gnu.org/g:895ec1956a1d8e4338760afae4e62829ba53ea7d commit r14-4341-g895ec1956a1d8e4338760afae4e62829ba53ea7d Author: Patrick O'Neill <patrick@rivosinc.com> Date: Tue Sep 12 11:30:20 2023 -0700 check_GNU_style.py: Skip .md square bracket linting This testcase causes lots of false-positives for machine description files. contrib/ChangeLog: * check_GNU_style_lib.py: Skip machine description file bracket linting. Signed-off-by: Patrick O'Neill <patrick@rivosinc.com> Diff: --- contrib/check_GNU_style_lib.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/contrib/check_GNU_style_lib.py b/contrib/check_GNU_style_lib.py index 94a742941cf..5096b1333f3 100755 --- a/contrib/check_GNU_style_lib.py +++ b/contrib/check_GNU_style_lib.py @@ -182,6 +182,9 @@ class SquareBracketCheck: self.re = re.compile('\w\s+(\[)') def check(self, filename, lineno, line): + if filename.endswith('.md'): + return None + m = self.re.search(line) if m != None: return CheckError(filename, lineno,
reply other threads:[~2023-09-29 21:13 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230929211338.BB3433858D32@sourceware.org \ --to=poneill@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).