Hi everyone, As some of you might know, I have been working on GCC Rust over on GitHub https://github.com/Rust-GCC/gccrs. As the project is moving forward and enforcing GCC copyright assignments for contributors, I would like to create a branch on the GCC git repo to show the intention to be upstream with GCC someday.
I tried to push the branch towards the start of the year, but I hit an issue: ``` Enumerating objects: 4706, done. Counting objects: 100% (4706/4706), done. Delta compression using up to 8 threads Compressing objects: 100% (1699/1699), done. Writing objects: 100% (4412/4412), 3.33 MiB | 948.00 KiB/s, done. Total 4412 (delta 3058), reused 3869 (delta 2683) remote: Resolving deltas: 100% (3058/3058), completed with 271 local objects. remote: *** Invalid revision history for commit c7c6f785c8e893ec7bcacd1a2319ce309d2450f2: remote: *** The first line should be the subject of the commit, remote: *** followed by an empty line. remote: *** remote: *** Below are the first few lines of the revision history: remote: *** | Adding Rust target hook documentation remote: *** | Added powerpc target hook and improved aarch64 feature handling remote: *** | Added DEC Alpha target hook remote: *** | Added ARC target hook remote: *** | Created ARM target hook (at least preliminary support) remote: *** remote: *** Please amend the commit's revision history and try again. remote: error: hook declined to update refs/heads/gccrs To ssh://gcc.gnu.org/git/gcc.git ! [remote rejected] gcc-mirror -> gccrs (hook declined) ``` The commit message here is poorly formatted. To move forward, should I rebase the tree to fix this commit and force push to rewrite the history? Or is there a way to relax the rule for a new branch? Any advice would be welcome. Separately, some contributors have expressed interest in maintaining the GCC style communications of using a mailing list and irc. Is it reasonable for this project to get a r...@gcc.gnu.org? Thanks, --Phil
OpenPGP_signature
Description: OpenPGP digital signature
