Hi, Thomas Koenig via Gcc <gcc@gcc.gnu.org> writes:
> Am 25.06.24 um 21:08 schrieb Arsen Arsenović via Gcc: > >> Richard Biener <richard.guent...@gmail.com> writes: > >>> I'd welcome this - care to create a patch for >>> contrib/gcc-git-customization.sh? >> Sure - I've attached a partial patch. I didn't find the hook which runs >> on each push to check commits, so the current patch is minimal. Is that >> also in the tree? I could try hacking it to check commits. > > Will this also influence commits to, for example, github? In the sense that their contents will be changed, yes - commits are independent of remote, so their committer field is common for all remotes. However, since only the committer field changes, and usually commits are tracked by the author field, that might not be too big of an issue. I've been pushing to SourceHut and GitHub with a committer.email set to arsen at gcc dot gnu dot org for a while now, here are example commits from both: https://git.sr.ht/~arsen/gcc/commit/0290e3ce8c017701bc5f665daf5ea438b3cd996f https://github.com/ArsenArsen/gcc/commit/ee6cc90 Note that, in the latter, GitHub attributes the commit to a non-GitHub account as committer, but it is still attributed to my account by author, if that is of concern. Note also that GH verifies GPG by *committer* (which makes sense..). This is why it states that my commit is unverified - I never added my sourceware/gcc.gnu.org email to GH. -- Arsen Arsenović
signature.asc
Description: PGP signature
