From: Joseph Myers <joseph@codesourcery.com>
To: Philip Herron <philip.herron@embecosm.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: GCC Rust git branch
Date: Mon, 24 May 2021 16:24:38 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2105241618020.247381@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5b2057ae-039c-6805-20fe-133df71c120e@embecosm.com>
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
next prev parent reply other threads:[~2021-05-24 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 13:24 Philip Herron
2021-05-24 16:24 ` Joseph Myers [this message]
2022-06-08 12:36 ` Thomas Schwinge
2021-05-24 18:29 ` Mark Wielaard
2021-05-28 10:31 ` Philip Herron
2021-05-30 22:33 ` Mark Wielaard
2021-05-28 3:05 ` Thomas Fitzsimmons
2021-05-28 10:18 ` Philip Herron
2021-05-28 11:48 ` Marc Poulhiès
2021-05-30 22:49 ` Mark Wielaard
2021-05-28 3:22 ` Jason Merrill
2021-05-28 10:19 ` Philip Herron
2022-06-08 10:58 ` Document <gcc-rust@gcc.gnu.org> mailing list (was: GCC Rust git branch) Thomas Schwinge
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=alpine.DEB.2.22.394.2105241618020.247381@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=philip.herron@embecosm.com \
/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).