public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH][pushed] contrib: add 'contrib' to default dirs in update-copyright.py
Date: Sun, 15 Jan 2023 20:53:36 -0800	[thread overview]
Message-ID: <CA+=Sn1nfhyh2XurieKzAvq5ZacQZyEt-Ghk7fJcz+vvEWWo0WQ@mail.gmail.com> (raw)
In-Reply-To: <6973c338-686e-618c-4e1a-1bbd75369ff8@suse.cz>

On Thu, Jan 5, 2023 at 11:49 PM Martin Liška <mliska@suse.cz> wrote:
>
> Hi.
>
> I forgot to include contrib folder in default dir, thus the copyright in the folder
> haven't been updated by Jakub.
>
> However, I noticed when I run ./contrib/update-copyright.py --this-year
> I get much more modifications out of contrib folder:
>
> $ git diff --stat
> ...
>  951 files changed, 976 insertions(+), 979 deletions(-)
>
> where the are not updated files is:
> gcc/analyzer/*
> gcc/common/config/*
> gcc/m2/*
> gcc/objc/*

libstdc++-v3 was not updated either. I wonder how many more were missed too ...

Thanks,
Andrew Pinski

>
> Jakub, can you please re-run the script?
>
> Cheers,
> Martin
>
> contrib/ChangeLog:
>
>         * update-copyright.py: Add contrib as a default dir.
> ---
>  contrib/update-copyright.py | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/contrib/update-copyright.py b/contrib/update-copyright.py
> index fcae846fb1e..06e6fb61757 100755
> --- a/contrib/update-copyright.py
> +++ b/contrib/update-copyright.py
> @@ -785,6 +785,7 @@ class GCCCmdLine (CmdLine):
>
>          self.default_dirs = [
>              'c++tools',
> +            'contrib',
>              'gcc',
>              'include',
>              'libada',
> --
> 2.39.0
>

      parent reply	other threads:[~2023-01-16  4:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06  7:49 Martin Liška
2023-01-10  7:53 ` Martin Liška
2023-01-16  4:53 ` Andrew Pinski [this message]

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='CA+=Sn1nfhyh2XurieKzAvq5ZacQZyEt-Ghk7fJcz+vvEWWo0WQ@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).