GCC Rust git branch

[Joseph Myers]

On Mon, 24 May 2021, Philip Herron wrote:

> remote: error: hook declined to update refs/heads/gccrs

refs/heads/gccrs doesn't match the branch naming conventions as documented 
at https://gcc.gnu.org/git.html (where you'd use refs/heads/devel/* for 
shared development branches), so if you hadn't had commit message 
formatting issues, the push would have been rejected for bad branch naming 
as well.

> 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.

If the community desires to relax the checks in a particular case, the way 
to do it would probably be to set hooks.no-precommit-check, naming the 
agreed branch name, temporarily in refs/meta/config:project.config, then 
revert that project.config change afterwards.  See 
https://github.com/AdaCore/git-hooks for the detailed documentation of 
hook configuration.

-- 
Joseph S. Myers
joseph@codesourcery.com