From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Marius Bakke <marius@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: branch staging updated: gnu: ghc-7: Clean up package definition.
Date: Tue, 2 Jun 2020 23:13:08 +0200 [thread overview]
Message-ID: <20200602211308.fqbrw4axxknff6of@gravity> (raw)
In-Reply-To: <87tuztuson.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
On Tue, Jun 02, 2020 at 10:19:20PM +0200, Marius Bakke wrote:
> Jakub Kądziołka <kuba@kadziolka.net> writes:
>
> > On Tue, Jun 02, 2020 at 09:22:31PM +0200, Marius Bakke wrote:
> >> We should have a better way to poll branch status other than "read all
> >> messages on guix-devel" or "ask Marius on IRC".
> >
> > Ouch, sorry for that! I see two potential solutions:
> >
> > 1. Have a guix-devel-announce mailing list, to which we would post
> > things concerning all Guix developers.
>
> Actually we already have an underutilized 'info-guix' list. I suppose
> that can work.
Huh, I thought this was for communicating to Guix users.
> > 2. Configure the git server to reject pushes to frozen branches when
> > unless --force is used.
>
> It will be difficult for the server to distinguish between 'bug fixes'
> and 'huge rebuilds'. Not sure if the --force flag propagates to servers
> the way you are thinking of, but perhaps it can work (not a great habit
> though!).
From the various behaviors of git servers I have observed, I would be
really surprised if it wasn't...
> Also, we'd have to bother the Savannah admins every time we 'freeze' a
> branch.
I suppose we could have a dotfile in the repository...
> Another option could be to create a tracking bug with a special tag that
> can be displayed by issues.guix.gnu.org. It could also show any merge
> blockers such as <https://issues.guix.gnu.org/issue/41598> to make it
> easier to contribute.
Makes sense. We'd need to update the Commit Access section accordingly.
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-02 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200601154315.6307.59562@vcs0.savannah.gnu.org>
2020-06-02 19:22 ` branch staging updated: gnu: ghc-7: Clean up package definition Marius Bakke
2020-06-02 19:45 ` Jakub Kądziołka
2020-06-02 20:19 ` Marius Bakke
2020-06-02 21:13 ` Jakub Kądziołka [this message]
2020-06-02 22:10 ` zimoun
2020-06-02 22:02 ` zimoun
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=20200602211308.fqbrw4axxknff6of@gravity \
--to=kuba@kadziolka.net \
--cc=guix-devel@gnu.org \
--cc=marius@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.