From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org, jsm28@gcc.gnu.org
Subject: Re: [PATCH] contrib: add contrib to update-copyright.py script
Date: Wed, 14 Dec 2022 14:13:12 +0100 [thread overview]
Message-ID: <Y5nL6DidazbpXMP6@tucnak> (raw)
In-Reply-To: <a95b8b6e-5685-52fa-0190-793eede45b19@suse.cz>
On Wed, Dec 14, 2022 at 02:10:32PM +0100, Martin Liška wrote:
> +class ContribFilder(GenericFilter):
s/Filder/Filter/g ?
> + def __init__ (self):
> + GenericFilter.__init__ (self)
> +
> + self.skip_files |= set ([
> + # A different copyrights.
> + 'unicode-license.txt',
> + 'Info.plist',
> + # Contains CR (^M).
> + 'repro_fail',
> + ])
> +
> class GCCCopyright (Copyright):
> def __init__ (self, errors):
> Copyright.__init__ (self, errors)
> @@ -699,6 +711,7 @@ class GCCCopyright (Copyright):
> self.add_external_author ('Advanced Micro Devices Inc.')
> self.add_external_author ('Ami Tavory and Vladimir Dreizin, IBM-HRL.')
> self.add_external_author ('Cavium Networks.')
> + self.add_external_author ('David Malcolm')
> self.add_external_author ('Faraday Technology Corp.')
> self.add_external_author ('Florida State University')
> self.add_external_author ('Gerard Jungman')
> @@ -738,7 +751,7 @@ class GCCCmdLine (CmdLine):
> # boehm-gc is imported from upstream.
> self.add_dir ('c++tools')
> self.add_dir ('config', ConfigFilter())
> - # contrib isn't really part of GCC.
> + self.add_dir ('contrib', ContribFilder())
> self.add_dir ('fixincludes')
> self.add_dir ('gcc', GCCFilter())
> self.add_dir (os.path.join ('gcc', 'testsuite'), TestsuiteFilter())
Jakub
next prev parent reply other threads:[~2022-12-14 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 13:10 Martin Liška
2022-12-14 13:13 ` Jakub Jelinek [this message]
2022-12-28 9:23 ` Martin Liška
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=Y5nL6DidazbpXMP6@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jsm28@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).