public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-5441] contrib: Ignore the r14-5312-g040e5b0edbca861196d9e2ea2af5e805769c8d5d bogus commit
Date: Tue, 14 Nov 2023 12:19:24 +0000 (GMT)	[thread overview]
Message-ID: <20231114121924.EE1213858CD1@sourceware.org> (raw)

https://gcc.gnu.org/g:0a1dd8b551e5b34b16394ff92e83c66275a85b9a

commit r14-5441-g0a1dd8b551e5b34b16394ff92e83c66275a85b9a
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Nov 14 13:09:43 2023 +0100

    contrib: Ignore the r14-5312-g040e5b0edbca861196d9e2ea2af5e805769c8d5d bogus commit
    
    The r14-5312-g040e5b0edbca861196d9e2ea2af5e805769c8d5d commit log contains
    a line from git revert with correct hash, but unfortunately hand ammended
    with explanation, so it got through the pre-commit hook but failed during
    update_version_git generation.  Please don't do this.
    
    2023-11-14  Jakub Jelinek  <jakub@redhat.com>
    
    contrib/ChangeLog:
            * gcc-changelog/git_update_version.py: Add
            040e5b0edbca861196d9e2ea2af5e805769c8d5d to ignored commits.

Diff:
---
 contrib/gcc-changelog/git_update_version.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/contrib/gcc-changelog/git_update_version.py b/contrib/gcc-changelog/git_update_version.py
index 3c438bba892..84767b07f0d 100755
--- a/contrib/gcc-changelog/git_update_version.py
+++ b/contrib/gcc-changelog/git_update_version.py
@@ -37,7 +37,8 @@ IGNORED_COMMITS = (
         '3ab5c8cd03d92bf4ec41e351820349d92fbc40c4',
         '86d8e0c0652ef5236a460b75c25e4f7093cc0651',
         'e4cba49413ca429dc82f6aa2e88129ecb3fdd943',
-        '1957bedf29a1b2cc231972aba680fe80199d5498')
+        '1957bedf29a1b2cc231972aba680fe80199d5498',
+        '040e5b0edbca861196d9e2ea2af5e805769c8d5d')
 
 FORMAT = '%(asctime)s:%(levelname)s:%(name)s:%(message)s'
 logging.basicConfig(level=logging.INFO, format=FORMAT,

                 reply	other threads:[~2023-11-14 12:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231114121924.EE1213858CD1@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).