From: Joel Brobecker <brobecker@adacore.com>
To: "Martin Liška" <mliska@suse.cz>,
Binutils <binutils@sourceware.org>,
gdb-patches@sourceware.org
Subject: Re: Please enable fast forward for user branches
Date: Tue, 30 Mar 2021 16:52:12 +0400 [thread overview]
Message-ID: <20210330125212.GG11111@adacore.com> (raw)
In-Reply-To: <YGMRVYlqQi7Q5bdR@vapier>
> > Actually, we do use the git-hooks (https://github.com/adacore/git-hooks)
> > which allow per-reference configuration of that restriction. That's
> > what I was trying to explain in my message.
>
> gotcha
>
> iiuc, the hooks are only accessible to a handful of devs who have admin
> access (i.e. ssh terminal on sourceware.org). could we move these to
> git themselves ? in past admin roles, i'd setup the hooks as yet another
> git repo for people to clone so people could send patches, or if review
> systems were available, to send PR's. only admins could approve, but
> everyone could still contribute & review directly.
The configuration is actually already accessible through Git,
inside the repository itself. The location is inspired from Gerrit:
It's in a file called project.config in the special reference
refs/meta/config.
The hooks themselves are under GitHub, and there is what I hope
a good reference README.md file that explains how to use the hooks.
--
Joel
prev parent reply other threads:[~2021-03-30 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1af95023-580d-6774-c307-1a38bf3dc073@suse.cz>
2021-03-30 4:09 ` Joel Brobecker
2021-03-30 5:36 ` Mike Frysinger via Gdb-patches
2021-03-30 6:17 ` Joel Brobecker
2021-03-30 11:53 ` Mike Frysinger via Gdb-patches
2021-03-30 12:52 ` Joel Brobecker [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=20210330125212.GG11111@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=mliska@suse.cz \
/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