On Thu, 3 Feb 2022, David Seifert via Gcc-patches wrote: > On Thu, 2022-02-03 at 12:50 +0100, Jakub Jelinek wrote: > > On Thu, Feb 03, 2022 at 12:30:11PM +0100, David Seifert wrote: > > > * `-Werror` can cause issues when a more recent version of GCC > > > compiles > > > ? an older version: > > > ? - https://bugs.gentoo.org/229059 > > > ? - https://bugs.gentoo.org/475350 > > > ? - https://bugs.gentoo.org/667104 > > > > > > libatomic/ChangeLog: > > > > > > ??????? * libatomic/configure.ac: Support --disable-werror. > > > ??????? * libatomic/configure: Regenerate. > > > > > > libbacktrace/ChangeLog: > > > > > > ??????? * libbacktrace/configure.ac: Support --disable-werror. > > > ??????? * libbacktrace/configure: Regenerate. > > > > > > libgo/ChangeLog: > > > > > > ??????? * libgo/configure.ac: Support --disable-werror. > > > ??????? * libgo/configure: Regenerate. > > > > > > libgomp/ChangeLog: > > > > > > ??????? * libgomp/configure.ac: Support --disable-werror. > > > ??????? * libgomp/configure: Regenerate. > > > > > > libitm/ChangeLog: > > > > > > ??????? * libitm/configure.ac: Support --disable-werror. > > > ??????? * libitm/configure: Regenerate. > > > > > > libsanitizer/ChangeLog: > > > > > > ??????? * libsanitizer/configure.ac: Support --disable-werror. > > > ??????? * libsanitizer/libbacktrace/Makefile.am (WARN_FLAGS): > > > Remove. > > > > As Jonathan wrote, if you don't have a copyright assignment on file, > > we need either that copyright assignment or the patch needs to be > > submitted according to https://gcc.gnu.org/dco.html?which is > > expressed by Signed-off-by line in the mail and commit message. > > > > I have an FSF copyright assignment, is there anything you need me to do > to this end?
Perhaps that assignment is still being processed, or under another name not matching Seifert? I couldn't find an entry case-insensitively matching that in a freshly retrieved copyright.list. brgds, H-P
