all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: "Leo Famulari" <leo@famulari.name>, "Mark H Weaver" <mhw@netris.org>
Cc: guix-devel@gnu.org, mail@nicolasgoaziou.fr
Subject: Re: branch staging updated (5aeee07 -> 104151f)
Date: Sun, 31 Jan 2021 10:59:58 +0100	[thread overview]
Message-ID: <C8X97V8ZHOFG.1MH5GHRUX0BFI@gravity> (raw)
In-Reply-To: <YBY9tEN4GO8VG2gl@jasmine.lan>

On Sun Jan 31, 2021 at 6:18 AM CET, Leo Famulari wrote:
> On Sat, Jan 30, 2021 at 06:37:11PM -0500, Mark H Weaver wrote:
> > What would the Git hook do, precisely?  The reason I ask is that some
> > bug fixes are appropriate on a frozen branch.  How would a Git hook
> > determine whether a given commit should be allowed?
>
> I haven't given much thought to how it would work but, if it ran on the
> client side as a pre-push hook, it could be easily disabled by the
> committer, when necessary.

Alternatively, one could include some control sequence in the commit
message. For example,

Allow-Frozen: staging

Regards,
Jakub Kądziołka


  reply	other threads:[~2021-01-31 10:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210129220535.30446.38250@vcs0.savannah.gnu.org>
2021-01-30 23:20 ` branch staging updated (5aeee07 -> 104151f) Leo Famulari
2021-01-30 23:37   ` Mark H Weaver
2021-01-31  5:18     ` Leo Famulari
2021-01-31  9:59       ` Jakub Kądziołka [this message]
2021-01-31 21:09         ` Mark H Weaver
2021-02-01 11:14           ` Hartmut Goebel
2021-02-01 11:28             ` Efraim Flashner
2021-02-01 19:39               ` Mark H Weaver
2021-02-01 20:43                 ` Christopher Baines
2021-02-01 20:56                   ` Leo Famulari

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=C8X97V8ZHOFG.1MH5GHRUX0BFI@gravity \
    --to=kuba@kadziolka.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=mail@nicolasgoaziou.fr \
    --cc=mhw@netris.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.