From: Martin Liska <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 3/3] mklog: Do not print changed functions in testsuite
Date: Tue, 13 Aug 2019 07:51:00 -0000 [thread overview]
Message-ID: <2a10fc201e35c10c38a68511a780d7aeb7ecec14.1565682592.git.mliska@suse.cz> (raw)
In-Reply-To: <cover.1565682592.git.mliska@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
contrib/ChangeLog:
2019-08-13 Martin Liska <mliska@suse.cz>
* mklog: Do not print changed functions for
testsuite files.
---
contrib/mklog | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0003-mklog-Do-not-print-changed-functions-in-testsuite.patch --]
[-- Type: text/x-patch; name="0003-mklog-Do-not-print-changed-functions-in-testsuite.patch", Size: 554 bytes --]
diff --git a/contrib/mklog b/contrib/mklog
index 85242002357..1a0e82d1ddd 100755
--- a/contrib/mklog
+++ b/contrib/mklog
@@ -407,7 +407,8 @@ otherwise writes to stdout.'
change_msg = ": Remove.\n"
_, ext = os.path.splitext(d.filename)
- if not change_msg and ext in ['.c', '.cpp', '.C', '.cc', '.h', '.inc', '.def']:
+ if (not change_msg and ext in ['.c', '.cpp', '.C', '.cc', '.h', '.inc', '.def']
+ and not 'testsuite' in d.filename):
fns = []
for hunk in d.hunks:
for fn in find_changed_funs(hunk):
next prev parent reply other threads:[~2019-08-13 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 7:51 [PATCH 0/3] mklog improvements Martin Liska
2019-08-13 7:51 ` Martin Liska [this message]
2019-08-13 7:57 ` [PATCH 2/3] mklog: parse PR references from new test files Martin Liska
2019-08-13 8:18 ` [PATCH 1/3] Use argparse.ArgumentParser for mklog Martin Liska
2019-08-30 9:24 ` [PATCH 0/3] mklog improvements Martin Liška
2019-09-03 16:37 ` Jeff Law
2019-09-04 8:05 ` Martin Liška
2019-09-04 14:56 ` Jeff Law
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=2a10fc201e35c10c38a68511a780d7aeb7ecec14.1565682592.git.mliska@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).