From: Thomas Schwinge <thomas@codesourcery.com>
To: Joseph Myers <joseph@codesourcery.com>,
Philip Herron <philip.herron@embecosm.com>,
<gcc-rust@gcc.gnu.org>, <gcc@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>
Subject: Re: GCC Rust git branch
Date: Wed, 8 Jun 2022 14:36:06 +0200 [thread overview]
Message-ID: <87czfjqqmh.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2105241618020.247381@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]
Hi!
This is about GCC/Rust, <https://rust-gcc.github.io/>, now also having a
presence in GCC upstream Git sources; see also
<https://github.com/Rust-GCC/gccrs/issues/143> "GCC Git Branch".
On 2021-05-24T16:24:38+0000, Joseph Myers <joseph@codesourcery.com> wrote:
> 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.
Thanks. I've thus pushed to refs/meta/config branch
commit 15e03be6fc6406e41c75ff95a9de449663fc9f0e "Enable
'no-precommit-check' for GCC/Rust development branches, 'devel/rust/*'",
see attached.
I've further pushed to gcc-wwwdocs
commit 325020ef06c714fbfd508d57e3f0bda272470464
"Document Git branch devel/rust/master", see attached.
I've also set up GCC Bugzilla:
- Add new component *rust*:
<https://gcc.gnu.org/bugzilla/editcomponents.cgi?action=edit&product=gcc&component=rust>.
- Add new version *rust/master*:
<https://gcc.gnu.org/bugzilla/editversions.cgi?action=edit&product=gcc&version=rust%2Fmaster>.
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Enable-no-precommit-check-for-GCC-Rust-development-b.patch --]
[-- Type: text/x-diff, Size: 931 bytes --]
From 15e03be6fc6406e41c75ff95a9de449663fc9f0e Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Wed, 8 Jun 2022 12:00:04 +0200
Subject: [PATCH] Enable 'no-precommit-check' for GCC/Rust development
branches, 'devel/rust/*'
---
project.config | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/project.config b/project.config
index b7bdaf30b9e..5905fe26272 100644
--- a/project.config
+++ b/project.config
@@ -87,3 +87,9 @@
# Custom email formatter. This inserts GCC monotonically
# increasing commit ids in the commit emails.
commit-email-formatter = /git/gcc.git/hooks-bin/commit_email_formatter
+
+ # For GCC/Rust development that happens outside of GCC proper,
+ # <https://rust-gcc.github.io/>, the Git commit messages
+ # don't always adhere to standard GCC style; see
+ # <https://github.com/Rust-GCC/gccrs/issues/143>.
+ no-precommit-check = refs/heads/devel/rust/.*
--
2.35.1
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0001-Document-Git-branch-devel-rust-master.patch --]
[-- Type: text/x-diff, Size: 940 bytes --]
From 325020ef06c714fbfd508d57e3f0bda272470464 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Wed, 8 Jun 2022 14:21:06 +0200
Subject: [PATCH] Document Git branch devel/rust/master
---
htdocs/git.html | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/htdocs/git.html b/htdocs/git.html
index 5fbd98bf..f9acea54 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -349,6 +349,12 @@ in Git.</p>
implementation of Fortran coarrays. It is maintained by
<a href="mailto:koenigni@gcc.gnu.org">Nicolas König</a>.</dd>
+ <dt><a href="https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=shortlog;h=refs/heads/devel/rust/master">devel/rust/master</a></dt>
+ <dd>
+ This branch is for development of
+ <a href="https://gcc.gnu.org/wiki/RustFrontEnd">Rust programming language
+ support in GCC</a>.
+ </dd>
</dl>
<h3 id="distrobranches">Distribution Branches</h3>
--
2.35.1
prev parent reply other threads:[~2022-06-08 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b2057ae-039c-6805-20fe-133df71c120e@embecosm.com>
[not found] ` <CADzB+2=63yKAj0GAq6XN+v+U+6g0VzHcEbm1VfYx_Vdg4UB1hg@mail.gmail.com>
[not found] ` <41c2376e-3b0e-7e32-5094-468caa692138@embecosm.com>
2022-06-08 10:58 ` Document <gcc-rust@gcc.gnu.org> mailing list (was: GCC Rust git branch) Thomas Schwinge
[not found] ` <alpine.DEB.2.22.394.2105241618020.247381@digraph.polyomino.org.uk>
2022-06-08 12:36 ` Thomas Schwinge [this message]
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=87czfjqqmh.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--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).