mirrors/binutils-gdb
0
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-12-01 05:55:23 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity
bb2981798f
binutils-gdb/gdb/copyright.py

430 lines
13 KiB
Python
Raw Normal View History

gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
#! /usr/bin/env python3
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
Update copyright year range in header of all files managed by GDB This commit is the result of the following actions: - Running gdb/copyright.py to update all of the copyright headers to include 2024, - Manually updating a few files the copyright.py script told me to update, these files had copyright headers embedded within the file, - Regenerating gdbsupport/Makefile.in to refresh it's copyright date, - Using grep to find other files that still mentioned 2023. If these files were updated last year from 2022 to 2023 then I've updated them this year to 2024. I'm sure I've probably missed some dates. Feel free to fix them up as you spot them.
2024-01-12 23:30:44 +08:00
# Copyright (C) 2011-2024 Free Software Foundation, Inc.
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
#
# This file is part of GDB.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
"""copyright.py
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
This script updates the list of years in the copyright notices in
most files maintained by the GDB project.
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
Usage: cd src/gdb && ./copyright.py
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
Always review the output of this script before committing it!
A useful command to review the output is:
% filterdiff -x \*.c -x \*.cc -x \*.h -x \*.exp updates.diff
This removes the bulk of the changes which are most likely to be correct.
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
"""
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
import argparse
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
import datetime
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
import locale
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
import os
import os.path
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
import subprocess
gdb/copyright.py: Exit if run from the wrong directory We printed an error, but kept going anyway... ;-) gdb/ChangeLog: * copyright.py (main): Exit if run from the wrong directory.
2020-01-01 13:08:08 +08:00
import sys
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
from typing import List, Optional
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
def get_update_list():
"""Return the list of files to update.
Assumes that the current working directory when called is the root
of the GDB source tree (NOT the gdb/ subdirectory!). The names of
the files are relative to that root directory.
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
"""
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
result = []
gdb/copyright.py: Also update sources in "gdbserver" and "gdbsupport" This commit adjusts GDB's copyright.py script, following two past changes: - gdb/gdbserver/ being move to the toplevel directory; - gdb/common/ being renamed to gdbsupport/. gdb/ChangeLog: * copyright.py (get_update_list): Add "gdbserver" and "gdbsupport" to the list of directories to update.
2021-01-01 15:56:12 +08:00
for gdb_dir in (
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"gdb",
"gdbserver",
"gdbsupport",
"gnulib",
"sim",
"include/gdb",
gdb/copyright.py: Also update sources in "gdbserver" and "gdbsupport" This commit adjusts GDB's copyright.py script, following two past changes: - gdb/gdbserver/ being move to the toplevel directory; - gdb/common/ being renamed to gdbsupport/. gdb/ChangeLog: * copyright.py (get_update_list): Add "gdbserver" and "gdbsupport" to the list of directories to update.
2021-01-01 15:56:12 +08:00
):
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
for root, dirs, files in os.walk(gdb_dir, topdown=True):
for dirname in dirs:
reldirname = "%s/%s" % (root, dirname)
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
if (
dirname in EXCLUDE_ALL_LIST
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
or reldirname in EXCLUDE_LIST
or reldirname in NOT_FSF_LIST
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
or reldirname in BY_HAND
):
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
# Prune this directory from our search list.
dirs.remove(dirname)
for filename in files:
relpath = "%s/%s" % (root, filename)
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
if (
filename in EXCLUDE_ALL_LIST
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
or relpath in EXCLUDE_LIST
or relpath in NOT_FSF_LIST
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
or relpath in BY_HAND
):
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
# Ignore this file.
pass
else:
result.append(relpath)
return result
def update_files(update_list):
"""Update the copyright header of the files in the given list.
We use gnulib's update-copyright script for that.
"""
Import gnulib's latest update-copyright script... ... and update our copyright.py script to set environment variable UPDATE_COPYRIGHT_USE_INTERVALS to '2' instead of '1'. This tells the script to collapse all years into one single interval. gdb/ChangeLog: * gnulib/extra/update-copyright: Update to the latest from gnulib's git repository. * copyright.py: Set UPDATE_COPYRIGHT_USE_INTERVALS environment variable to 2 instead of 1.
2012-03-01 10:41:04 +08:00
# We want to use year intervals in the copyright notices, and
# all years should be collapsed to one single year interval,
# even if there are "holes" in the list of years found in the
# original copyright notice (OK'ed by the FSF, case [gnu.org #719834]).
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
os.environ["UPDATE_COPYRIGHT_USE_INTERVALS"] = "2"
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
# Perform the update, and save the output in a string.
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
update_cmd = ["bash", "gnulib/import/extra/update-copyright"]
copyright.py: Update path to gnulib import. The location where we store the gnulib import has changed. This patch updates accordingly the path to gnulib's update-copyright script. gdb/ChangeLog: * copyright.py (update_files, main): Fix path to update-copyright script.
2012-06-05 21:29:07 +08:00
update_cmd += update_list
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
p = subprocess.Popen(
update_cmd,
stdout=subprocess.PIPE,
stderr=subprocess.STDOUT,
encoding=locale.getpreferredencoding(),
)
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
update_out = p.communicate()[0]
# Process the output. Typically, a lot of files do not have
# a copyright notice :-(. The update-copyright script prints
# a well defined warning when it did not find the copyright notice.
# For each of those, do a sanity check and see if they may in fact
# have one. For the files that are found not to have one, we filter
# the line out from the output, since there is nothing more to do,
# short of looking at each file and seeing which notice is appropriate.
# Too much work! (~4,000 files listed as of 2012-01-03).
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
update_out = update_out.splitlines(keepends=False)
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
warning_string = ": warning: copyright statement not found"
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
warning_len = len(warning_string)
for line in update_out:
if line.endswith(warning_string):
filename = line[:-warning_len]
if may_have_copyright_notice(filename):
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
print(line)
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
else:
# Unrecognized file format. !?!
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
print("*** " + line)
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
def may_have_copyright_notice(filename):
"""Check that the given file does not seem to have a copyright notice.
The filename is relative to the root directory.
This function assumes that the current working directory is that root
directory.
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
gdb: copyright: fix a few comment typos
2022-01-02 02:48:25 +08:00
The algorithm is fairly crude, meaning that it might return
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
some false positives. I do not think it will return any false
negatives... We might improve this function to handle more
complex cases later...
"""
# For now, it may have a copyright notice if we find the word
# "Copyright" at the (reasonable) start of the given file, say
# 50 lines...
MAX_LINES = 50
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
# We don't really know what encoding each file might be following,
# so just open the file as a byte stream. We only need to search
# for a pattern that should be the same regardless of encoding,
# so that should be good enough.
gdb: copyright: make file header scan a bit more pythonic Should be functionally the same, but uses more pythonic idioms to get fewer lines of code, and to make sure to not leak open file handles. Approved-By: Simon Marchi <simon.marchi@efficios.com>
2022-01-02 02:08:20 +08:00
with open(filename, "rb") as fd:
for lineno, line in enumerate(fd, start=1):
if b"Copyright" in line:
return True
if lineno > MAX_LINES:
break
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
return False
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
def get_parser() -> argparse.ArgumentParser:
"""Get a command line parser."""
parser = argparse.ArgumentParser(
description=__doc__, formatter_class=argparse.RawDescriptionHelpFormatter
)
return parser
def main(argv: List[str]) -> Optional[int]:
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
"""The main subprogram."""
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
parser = get_parser()
_ = parser.parse_args(argv)
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
root_dir = os.path.dirname(os.getcwd())
os.chdir(root_dir)
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
if not (
os.path.isdir("gdb") and os.path.isfile("gnulib/import/extra/update-copyright")
):
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
sys.exit("Error: This script must be called from the gdb directory.")
gdb/copyright.py: Adapt after move of gnulib from gdb to toplevel gdb/ChangeLog: * copyright.py: Adapt after move of gnulib directory from gdb directory to toplevel directory.
2020-01-01 13:19:14 +08:00
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
update_list = get_update_list()
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
update_files(update_list)
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
# Remind the user that some files need to be updated by HAND...
gdb/copyright.py: Do not forget to remind about MULTIPLE_COPYRIGHT_HEADERS There is a small logical error in the part of the script that dumps the list of files in BY_HAND + MULTIPLE_COPYRIGHT_HEADERS but only checkis the contents of BY_HAND. The issue becomes apparent as soon as BY_HAND is empty. Prevent this from happening by treating the two lists separately, as this allows us to provide a more informative message in the case of MULTIPLE_COPYRIGHT_HEADERS. gdb/ChangeLog: * copyright.py (main): Dump the contents of MULTIPLE_COPYRIGHT_HEADERS (separately) from BY_HAND, even if BY_HAND is empty.
2018-01-01 12:30:28 +08:00
if MULTIPLE_COPYRIGHT_HEADERS:
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
print()
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
print(
"\033[31m"
"REMINDER: Multiple copyright headers must be updated by hand:"
"\033[0m"
)
gdb/copyright.py: Do not forget to remind about MULTIPLE_COPYRIGHT_HEADERS There is a small logical error in the part of the script that dumps the list of files in BY_HAND + MULTIPLE_COPYRIGHT_HEADERS but only checkis the contents of BY_HAND. The issue becomes apparent as soon as BY_HAND is empty. Prevent this from happening by treating the two lists separately, as this allows us to provide a more informative message in the case of MULTIPLE_COPYRIGHT_HEADERS. gdb/ChangeLog: * copyright.py (main): Dump the contents of MULTIPLE_COPYRIGHT_HEADERS (separately) from BY_HAND, even if BY_HAND is empty.
2018-01-01 12:30:28 +08:00
for filename in MULTIPLE_COPYRIGHT_HEADERS:
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
print(" ", filename)
gdb/copyright.py: Do not forget to remind about MULTIPLE_COPYRIGHT_HEADERS There is a small logical error in the part of the script that dumps the list of files in BY_HAND + MULTIPLE_COPYRIGHT_HEADERS but only checkis the contents of BY_HAND. The issue becomes apparent as soon as BY_HAND is empty. Prevent this from happening by treating the two lists separately, as this allows us to provide a more informative message in the case of MULTIPLE_COPYRIGHT_HEADERS. gdb/ChangeLog: * copyright.py (main): Dump the contents of MULTIPLE_COPYRIGHT_HEADERS (separately) from BY_HAND, even if BY_HAND is empty.
2018-01-01 12:30:28 +08:00
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
if BY_HAND:
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
print()
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
print(
"\033[31mREMINDER: The following files must be updated by hand." "\033[0m"
)
gdb/copyright.py: Do not forget to remind about MULTIPLE_COPYRIGHT_HEADERS There is a small logical error in the part of the script that dumps the list of files in BY_HAND + MULTIPLE_COPYRIGHT_HEADERS but only checkis the contents of BY_HAND. The issue becomes apparent as soon as BY_HAND is empty. Prevent this from happening by treating the two lists separately, as this allows us to provide a more informative message in the case of MULTIPLE_COPYRIGHT_HEADERS. gdb/ChangeLog: * copyright.py (main): Dump the contents of MULTIPLE_COPYRIGHT_HEADERS (separately) from BY_HAND, even if BY_HAND is empty.
2018-01-01 12:30:28 +08:00
for filename in BY_HAND:
gdb/copyright.py: Convert to Python 3 gdb/ChangeLog: * copyright.py: Convert to Python 3.
2020-01-01 14:12:57 +08:00
print(" ", filename)
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
############################################################################
#
# Some constants, placed at the end because they take up a lot of room.
# The actual value of these constants is not significant to the understanding
# of the script.
#
############################################################################
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
# Files which should not be modified, either because they are
# generated, non-FSF, or otherwise special (e.g. license text,
# or test cases which must be sensitive to line numbering).
#
# Filenames are relative to the root directory.
EXCLUDE_LIST = (
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"gdb/nat/glibc_thread_db.h",
"gdb/CONTRIBUTE",
gdb/copyright.py: Do not update gdbsupport/Makefile.in This file is generated, so we should not modify it (any modification we make is going to be undone at the next re-generation anyway).
2022-01-16 17:50:38 +08:00
"gdbsupport/Makefile.in",
Add missing backslash to update-gnulib.sh A user on irc noticed a missing backslash on one line in update-gnulib.sh. This patch adds it. Re-running update-gnulib.sh causes a few copyright notices to change. Presumably these are from upstream gnulib and shouldn't be touched by our yearly update. I've updated the script to account for this, but I did not want to try testing it...
2023-05-31 20:27:16 +08:00
"gnulib/doc/gendocs_template",
"gnulib/doc/gendocs_template_min",
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"gnulib/import",
"gnulib/config.in",
"gnulib/Makefile.in",
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
)
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
# Files which should not be modified, either because they are
# generated, non-FSF, or otherwise special (e.g. license text,
# or test cases which must be sensitive to line numbering).
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
#
# Matches any file or directory name anywhere. Use with caution.
# This is mostly for files that can be found in multiple directories.
# Eg: We want all files named COPYING to be left untouched.
EXCLUDE_ALL_LIST = (
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"COPYING",
"COPYING.LIB",
"CVS",
"configure",
"copying.c",
"fdl.texi",
"gpl.texi",
"aclocal.m4",
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
)
# The list of files to update by hand.
BY_HAND = (
gdb/copyright.py: Remove testsuite/gdb.base/step-line.{c,inp} special handling In the past, these files needed to be handled by hand, because the testcase was sensitive to the length of the header, which was potentially changing when new copyright years were added to the copyright header. Now that we simply maintain and update a range, the length of the copyright header should not change as a consequence of the update performed by this script, so special handling of those files is no longer necessary. gdb/ChangeLog: * copyright.py (BY_HAND): Remove gdb/testsuite/gdb.base/step-line.inp and gdb/testsuite/gdb.base/step-line.c.
2018-01-01 12:18:16 +08:00
# Nothing at the moment :-).
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
)
copyright.py: Tell user to update gdb.texinfo and refcard.tex by hand. gdb/ChangeLog: * copyright.py (MULTIPLE_COPYRIGHT_HEADERS): New constant. (main): Add MULTIPLE_COPYRIGHT_HEADERS to the list of files for which a reminder to update by hand is printed.
2012-06-05 21:28:59 +08:00
# Files containing multiple copyright headers. This script is only
# fixing the first one it finds, so we need to finish the update
# by hand.
MULTIPLE_COPYRIGHT_HEADERS = (
"gdb/doc/gdb.texinfo",
"gdb/doc/refcard.tex",
gdb/copyright.py: Add update-netbsd.sh to MULTIPLE_COPYRIGHT_HEADERS Add gdb/syscalls/update-netbsd.sh to the reminder printed at the end of the execution listing all the files where a manual update of the copyright header is needed. This scripts contains some inline code which includes a copyright header.
2022-01-01 23:03:38 +08:00
"gdb/syscalls/update-netbsd.sh",
copyright.py: Tell user to update gdb.texinfo and refcard.tex by hand. gdb/ChangeLog: * copyright.py (MULTIPLE_COPYRIGHT_HEADERS): New constant. (main): Add MULTIPLE_COPYRIGHT_HEADERS to the list of files for which a reminder to update by hand is printed.
2012-06-05 21:28:59 +08:00
)
gdb: copyright: fix a few comment typos
2022-01-02 02:48:25 +08:00
# The list of file which have a copyright, but not held by the FSF.
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
# Filenames are relative to the root directory.
NOT_FSF_LIST = (
"gdb/exc_request.defs",
"gdb/gdbtk",
"gdb/testsuite/gdb.gdbtk/",
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"sim/arm/armemu.h",
"sim/arm/armos.c",
"sim/arm/gdbhost.c",
"sim/arm/dbg_hif.h",
"sim/arm/dbg_conf.h",
"sim/arm/communicate.h",
"sim/arm/armos.h",
"sim/arm/armcopro.c",
"sim/arm/armemu.c",
"sim/arm/kid.c",
"sim/arm/thumbemu.c",
"sim/arm/armdefs.h",
"sim/arm/armopts.h",
"sim/arm/dbg_cp.h",
"sim/arm/dbg_rdi.h",
"sim/arm/parent.c",
"sim/arm/armsupp.c",
"sim/arm/armrdi.c",
"sim/arm/bag.c",
"sim/arm/armvirt.c",
"sim/arm/main.c",
"sim/arm/bag.h",
"sim/arm/communicate.c",
"sim/arm/gdbhost.h",
"sim/arm/armfpe.h",
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
"sim/arm/arminit.c",
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"sim/common/cgen-fpu.c",
"sim/common/cgen-fpu.h",
Update copyright.py:NOT_FSF_LIST for sim/common subdir. There was a duplicate ("sim/common/cgen-fpu.h"), and one entry where we do have an FSF copyright header ("sim/common/sim-fpu.c"). gdb/ChangeLog: * copyright.py (NOT_FSF_LIST): Remove duplicate entry "sim/common/cgen-fpu.h". Remove invalid entries "sim/common/sim-fpu.c" and "sim/mn10300/sim-main.h", which actually have an FSF copyright header.
2012-12-07 18:00:57 +08:00
"sim/common/cgen-accfp.c",
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"sim/mips/m16run.c",
"sim/mips/sim-main.c",
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
"sim/moxie/moxie-gdb.dts",
# Not a single file in sim/ppc/ appears to be copyright FSF :-(.
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"sim/ppc/filter.h",
"sim/ppc/gen-support.h",
"sim/ppc/ld-insn.h",
"sim/ppc/hw_sem.c",
"sim/ppc/hw_disk.c",
"sim/ppc/idecode_branch.h",
"sim/ppc/sim-endian.h",
"sim/ppc/table.c",
"sim/ppc/hw_core.c",
"sim/ppc/gen-support.c",
"sim/ppc/gen-semantics.h",
"sim/ppc/cpu.h",
"sim/ppc/sim_callbacks.h",
"sim/ppc/RUN",
"sim/ppc/Makefile.in",
"sim/ppc/emul_chirp.c",
"sim/ppc/hw_nvram.c",
"sim/ppc/dc-test.01",
"sim/ppc/hw_phb.c",
"sim/ppc/hw_eeprom.c",
"sim/ppc/bits.h",
"sim/ppc/hw_vm.c",
"sim/ppc/cap.h",
"sim/ppc/os_emul.h",
"sim/ppc/options.h",
"sim/ppc/gen-idecode.c",
"sim/ppc/filter.c",
"sim/ppc/corefile-n.h",
"sim/ppc/std-config.h",
"sim/ppc/ld-decode.h",
"sim/ppc/filter_filename.h",
"sim/ppc/hw_shm.c",
"sim/ppc/pk_disklabel.c",
"sim/ppc/dc-simple",
"sim/ppc/misc.h",
"sim/ppc/device_table.h",
"sim/ppc/ld-insn.c",
"sim/ppc/inline.c",
"sim/ppc/emul_bugapi.h",
"sim/ppc/hw_cpu.h",
"sim/ppc/debug.h",
"sim/ppc/hw_ide.c",
"sim/ppc/debug.c",
"sim/ppc/gen-itable.h",
"sim/ppc/interrupts.c",
"sim/ppc/hw_glue.c",
"sim/ppc/emul_unix.c",
"sim/ppc/sim_calls.c",
"sim/ppc/dc-complex",
"sim/ppc/ld-cache.c",
"sim/ppc/registers.h",
"sim/ppc/dc-test.02",
"sim/ppc/options.c",
"sim/ppc/igen.h",
"sim/ppc/registers.c",
"sim/ppc/device.h",
"sim/ppc/emul_chirp.h",
"sim/ppc/hw_register.c",
"sim/ppc/hw_init.c",
"sim/ppc/sim-endian-n.h",
"sim/ppc/filter_filename.c",
"sim/ppc/bits.c",
"sim/ppc/idecode_fields.h",
"sim/ppc/hw_memory.c",
"sim/ppc/misc.c",
"sim/ppc/double.c",
"sim/ppc/psim.h",
"sim/ppc/hw_trace.c",
"sim/ppc/emul_netbsd.h",
"sim/ppc/psim.c",
gdb/copyright.py: Adjust following rename of sim/ppc/ppc-instructions... ... to sim/ppc/powerpc.igen This file is in the NOT_FSF_LIST because this file has a copyright which is not assigned to the FSF. Since the file got renamed, the corresponding entry in NOT_FSF_LIST needs to be renamed as well.
2023-01-01 20:47:26 +08:00
"sim/ppc/powerpc.igen",
gdb: re-format Python files using black 21.4b0 Re-format all Python files using black [1] version 21.4b0. The goal is that from now on, we keep all Python files formatted using black. And that we never have to discuss formatting during review (for these files at least) ever again. One change is needed in gdb.python/py-prettyprint.exp, because it matches the string representation of an exception, which shows source code. So the change in formatting must be replicated in the expected regexp. To document our usage of black I plan on adding this to the "GDB Python Coding Standards" wiki page [2]: --8<-- All Python source files under the `gdb/` directory must be formatted using black version 21.4b0. This specific version can be installed using: $ pip3 install 'black == 21.4b0' All you need to do to re-format files is run `black <file/directory>`, and black will re-format any Python file it finds in there. It runs quite fast, so the simplest is to do: $ black gdb/ from the top-level. If you notice that black produces changes unrelated to your patch, it's probably because someone forgot to run it before you. In this case, don't include unrelated hunks in your patch. Push an obvious patch fixing the formatting and rebase your work on top of that. -->8-- Once this is merged, I plan on setting a up an `ignoreRevsFile` config so that git-blame ignores this commit, as described here: https://github.com/psf/black#migrating-your-code-style-without-ruining-git-blame I also plan on working on a git commit hook (checked in the repo) to automatically check the formatting of the Python files on commit. [1] https://pypi.org/project/black/ [2] https://sourceware.org/gdb/wiki/Internals%20GDB-Python-Coding-Standards gdb/ChangeLog: * Re-format all Python files using black. gdb/testsuite/ChangeLog: * Re-format all Python files using black. * gdb.python/py-prettyprint.exp (run_lang_tests): Adjust. Change-Id: I28588a22c2406afd6bc2703774ddfff47cd61919
2021-05-07 22:56:20 +08:00
"sim/ppc/tree.h",
"sim/ppc/README",
"sim/ppc/gen-icache.h",
"sim/ppc/gen-model.h",
"sim/ppc/ld-cache.h",
"sim/ppc/mon.c",
"sim/ppc/corefile.h",
"sim/ppc/vm.c",
"sim/ppc/INSTALL",
"sim/ppc/gen-model.c",
"sim/ppc/hw_cpu.c",
"sim/ppc/corefile.c",
"sim/ppc/hw_opic.c",
"sim/ppc/gen-icache.c",
"sim/ppc/events.h",
"sim/ppc/os_emul.c",
"sim/ppc/emul_generic.c",
"sim/ppc/main.c",
"sim/ppc/hw_com.c",
"sim/ppc/gen-semantics.c",
"sim/ppc/emul_bugapi.c",
"sim/ppc/device.c",
"sim/ppc/emul_generic.h",
"sim/ppc/tree.c",
"sim/ppc/mon.h",
"sim/ppc/interrupts.h",
"sim/ppc/cap.c",
"sim/ppc/cpu.c",
"sim/ppc/hw_phb.h",
"sim/ppc/device_table.c",
"sim/ppc/lf.c",
"sim/ppc/lf.c",
"sim/ppc/dc-stupid",
"sim/ppc/hw_pal.c",
"sim/ppc/ppc-spr-table",
"sim/ppc/emul_unix.h",
"sim/ppc/words.h",
"sim/ppc/basics.h",
"sim/ppc/hw_htab.c",
"sim/ppc/lf.h",
"sim/ppc/ld-decode.c",
"sim/ppc/sim-endian.c",
"sim/ppc/gen-itable.c",
"sim/ppc/idecode_expression.h",
"sim/ppc/table.h",
"sim/ppc/dgen.c",
"sim/ppc/events.c",
"sim/ppc/gen-idecode.h",
"sim/ppc/emul_netbsd.c",
"sim/ppc/igen.c",
"sim/ppc/vm_n.h",
"sim/ppc/vm.h",
"sim/ppc/hw_iobus.c",
"sim/ppc/inline.h",
gdb: update sim mips testsuite copyright exemption The sim testsuite was reorganized last year, so update the path.
2022-01-02 02:03:51 +08:00
"sim/testsuite/mips/mips32-dsp2.s",
use gnulib's update-copyright script to update copyright years This patch now retires the old copyright.sh script which was using emacs to perform the copyright update. It also completely rewrite copyright.py to call update-copyright with the appropriate list of files. In addition to calling update-copyright, the new script also performs a sanity-check on all the files that update-copyright could not update, and sees whether the file might contain a copyright notice that the script could not decipher. gdb/ChangeLog: * copyright.sh: Delete. * copyright.py: Rewrite.
2012-01-04 15:55:48 +08:00
)
New script copyright.py gdb/ChangeLog: * copyright.py: New script. * copyright.sh (byhand): Add *.ads, *.adb, *.gpr and *.inc. Launch emacs without exec'ing. Call copyright.py afterwards.
2011-01-06 14:28:39 +08:00
if __name__ == "__main__":
gdb: make copyright.py interface a bit nicer This way people can run `./copyright.py --help` and get some info as to what this does without it going and modifying the tree.
2022-01-02 02:02:02 +08:00
sys.exit(main(sys.argv[1:]))
Reference in New Issue Copy Permalink