From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: git hook error
Date: Tue, 28 Dec 2021 23:45:48 +0100 [thread overview]
Message-ID: <87ee5wfhsm.fsf@nckx> (raw)
In-Reply-To: <871r1wicgr.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hi Ricardo,
Ricardo Wurmus 写道:
> - Savannah’s uptime isn’t quite as high as we’d like
I wonder if Savannah monitors and publishes numbers, and how they
compare to other popular forges.
Why should we do better? We haven't even managed to set up a git
mirror after all these years.
> - we can’t have server-side checks to prevent pushing bad
> commits
> - we can’t have server-side hooks to better integrate with the
> build farm
> - we can’t have per-branch rules (e.g. to allow contributors to
> push to
> some but not all branches)
Why not? Which of these can't be got with server-side hooks? How
would you get them on Guix infra then? Could the Savannah admins
accommodate us further, if needed?
If the real reason for even one of them is ‘well, we can, but
nobody wants to write those hooks’, that only bolsters my previous
scepticism.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-12-28 23:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 20:10 git hook error Ricardo Wurmus
2021-12-28 20:26 ` Tobias Geerinckx-Rice
2021-12-28 20:35 ` Leo Famulari
2021-12-28 21:09 ` Ricardo Wurmus
2021-12-28 21:40 ` Leo Famulari
2021-12-28 22:31 ` Ricardo Wurmus
2021-12-28 22:45 ` Tobias Geerinckx-Rice [this message]
2021-12-29 0:01 ` Tobias Geerinckx-Rice
2021-12-28 23:46 ` Leo Famulari
2021-12-29 8:53 ` zimoun
2021-12-28 23:32 ` raingloom
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee5wfhsm.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).