]> git.ipfire.org Git - thirdparty/gcc.git/commit
contrib/gcc-changelog: Check whether revert-commit exists
authorTobias Burnus <tobias@codesourcery.com>
Thu, 7 Sep 2023 10:52:37 +0000 (12:52 +0200)
committerTobias Burnus <tobias@codesourcery.com>
Thu, 7 Sep 2023 10:52:37 +0000 (12:52 +0200)
commit69e83181ebcb2edffd179a493d35d9a2a9612163
treee22e4bcb1b9552da05b18623dd648ecc3f8705d3
parentfbbd9001e9b6f2c59b542cc53a8f9183514091ce
contrib/gcc-changelog: Check whether revert-commit exists

This is the identical (except for a ChangeLog typo) to
  commit r14-3777-gff20bce9f5879878f352f1fcd6ade023a2067598

It reverts the test revert in commit
  r14-3778-gfbbd9001e9b6f2c59b542cc53a8f9183514091ce
which has a bogus commit hash and should have been rejected,
but we missed that - before testing - the script had to be
manually copied to the right place on sourceware to be
affective as pre-commit hook.

Thus, the r14-3777 commit had to be reinstate by this commit ...

contrib/ChangeLog:

* gcc-changelog/git_commit.py (GitCommit.__init__):
Handle commit_to_info_hook = None; otherwise, if None,
regard it as error.
(to_changelog_entries): Handle commit_to_info_hook = None;
if info is None, create a warning for it.
* gcc-changelog/git_email.py (GitEmail.__init__):
call super() with commit_to_info_hook=None instead
of a lambda function.
contrib/gcc-changelog/git_commit.py
contrib/gcc-changelog/git_email.py