commit error: Non-standard/badly formatted template - found
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 10 Nov 2023 18:00:41 UTC
Hi all, There is an error when I want to publish a commit: remote: remote: ================================================================ remote: Non-standard/badly formatted template - found 'Reviewers:' instead of 'Reviewed by:'. remote: ================================================================ remote: To ssh://repo.freebsd.org/ports.git I cannot find any errors in my commit message: databases/mysql57-{client, server}: Update to 5.7.43 Bugs Fixed: Group Replication: After one machine halted and restarted in a three-node MySQL InnoDB Cluster, one node failed to start; after restarting all nodes, the cluster shut down unexpectedly. Our thanks to Zetang Zeng for the contribution. (Bug #34976442) Fortified parsing of the network packet data sent by the server to the client. (Bug #35374491) Some floating-point literals were not always handled correctly. (Bug Executing a query with an implicit aggregation should return exactly one row, unless the query has a HAVING clause that filters out the row, but a query with a HAVING clause which evaluated to FALSE sometimes ignored this, and returned a row regardless. (Bug #14272020) During optimization, range-select tree creation uses logic which differs based on the left-hand side of the IN() predicate. For a field item, each value on the right-hand side is added to an OR tree to create the necessary expression. In the case of a row item comparison (example: WHERE (a,b) IN ((n1,m1), (n2, m2), ...)), an expression in disjunctive normal form (DNF) is needed. A DNF expression is created by adding an AND tree with column values to an OR tree for each set of RHS values, but instead the OR tree was added to the AND tree causing the tree merge to require exponential time due to O(n2) runtime complexity. (Bug See full Changlog here: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-43.html Sponsored by: Netzkommune GmbH # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # # category/port: Subject goes here, max 50 cols -| # <then a blank line> # 72 columns --| # # Do not add a Submitted by line. If someone besides the committer sent in the # change, the commit author should be set using `git commit --author`. # # Uncomment and complete these metadata fields, as appropriate: # # PR: <If and which Problem Report is related.> # Reported by: <If someone else reported the issue.> # Reviewed by: <If someone else reviewed your modification.> # Tested by: <If someone else tested the change.> # Approved by: <If you needed approval for this commit.> # Obtained from: <If the change is from a third party.> # Fixes: <Short hash and title line of commit fixed by this change> # MFH: <Ports tree branch name you plan to merge to.> # Relnotes: <Set to 'yes' for mention in release notes.> # Security: <Vulnerability reference (one per line) or description.> # Sponsored by: <If the change was sponsored by an organization.> # Pull Request: <https://github.com/freebsd/freebsd-ports/pull/###> # Differential Revision: <https://reviews.freebsd.org/D###> # # "Pull Request" and "Differential Revision" require the *full* GitHub or # Phabricator URL. # # Date: Fri Nov 10 18:25:02 2023 +0100 # # On branch main # Your branch is ahead of 'origin/main' by 2 commits. # (use "git push" to publish your local commits) # # Changes to be committed: # modified: databases/mysql57-client/files/patch-cmake_ssl.cmake # modified: databases/mysql57-server/Makefile # modified: databases/mysql57-server/distinfo # modified: databases/mysql57-server/files/patch-cmake_ssl.cmake I have set up my git according to this guideline: https://docs.freebsd.org/en/articles/committers-guide/#git-mini-daily-use Does anyone here have any tips? Cheers jochen