public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-3806] Update contrib + libgomp ChangeLogs for failed reject-commit testing
Date: Fri,  8 Sep 2023 10:03:18 +0000 (GMT)	[thread overview]
Message-ID: <20230908100319.1BAA03858418@sourceware.org> (raw)

https://gcc.gnu.org/g:478c37e72345307fad0aa06e0dae133eae206b0c

commit r14-3806-g478c37e72345307fad0aa06e0dae133eae206b0c
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Sep 8 12:02:02 2023 +0200

    Update contrib + libgomp ChangeLogs for failed reject-commit testing
    
    The following commit should have enabled checking for invalid revert hashes;
    it worked locally - but did work as pre-commit hook on sourceware
    as it wasn't copied to the hook directory:
    r14-3777-gff20bce9f58 contrib/gcc-changelog: Check whether revert-commit exists
    
    Hence, the following revert commit was wrongly applied:
    r14-3778-gfbbd9001e9b Revert "contrib/gcc-changelog: Check whether revert-commit exists"
    (In this commit: contrib/ChangeLog update for the revert.)
    
    r14-3779-g69e83181ebc contrib/gcc-changelog: Check whether revert-commit exists
    Re-applied the commit with a commit-log typo fixed but missing a late commit.
    
    r14-3780-g1b0934b7276 Revert "contrib/gcc-changelog: Check whether revert-commit exists"
    This commit still came through but re-instated the late wording fix in
    contrib/gcc-changelog/git_commit.py.
    (In this commit: contrib/ChangeLog update for the wording change.)
    
    r14-3781-gd22cd7745ff Revert: "Another revert test with a bogus hash"
    Another attempt to get a reject, but it still came through.
    It removed tailing whitespace in libgomp/target.c
    (In this commit: libgomp/ChangeLog was for the whitespace removal.)

Diff:
---
 contrib/ChangeLog | 19 +++++++++++++++++++
 libgomp/ChangeLog |  4 ++++
 2 files changed, 23 insertions(+)

diff --git a/contrib/ChangeLog b/contrib/ChangeLog
index e49bbe304465..403a095512c2 100644
--- a/contrib/ChangeLog
+++ b/contrib/ChangeLog
@@ -1,3 +1,8 @@
+2023-09-07  Tobias Burnus  <tobias@codesourcery.com>
+
+	* gcc-changelog/git_commit.py (GitCommit.__init__,
+	to_changelog_entries): Fix lost wording fix.
+
 2023-09-07  Tobias Burnus  <tobias@codesourcery.com>
 
 	* gcc-changelog/git_commit.py (GitCommit.__init__):
@@ -9,6 +14,20 @@
 	call super() with commit_to_info_hook=None instead
 	of a lambda function.
 
+2023-09-07  Tobias Burnus  <tobias@codesourcery.com>
+
+	Revert:
+	2023-09-07  Tobias Burnus  <tobias@codesourcery.com>
+
+	* 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 lamda function.
+
 2023-09-07  Tobias Burnus  <tobias@codesourcery.com>
 
 	* gcc-changelog/git_commit.py (GitCommit.__init__):
diff --git a/libgomp/ChangeLog b/libgomp/ChangeLog
index dbd5e4fc4ee7..fb96155394e1 100644
--- a/libgomp/ChangeLog
+++ b/libgomp/ChangeLog
@@ -5,6 +5,10 @@
 	omp_get_default_allocator.
 	(OMP_ALLOCATOR): Fix ICV var name; add see-also references.
 
+2023-09-07  Tobias Burnus  <tobias@codesourcery.com>
+
+	* target.c (gomp_unload_device): Remove tailing whitespace.
+
 2023-09-04  Tobias Burnus  <tobias@codesourcery.com>
 	    Thomas Schwinge  <thomas@codesourcery.com>

                 reply	other threads:[~2023-09-08 10:03 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=20230908100319.1BAA03858418@sourceware.org \
    --to=burnus@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).