From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Christopher Baines <mail@cbaines.net>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: Feature branches
Date: Mon, 8 May 2023 10:15:56 -0700 [thread overview]
Message-ID: <CAFHYt56fXA0bsMPbtJWRPzifjnYVjR0afO8b_dJaXy7tK=pEAQ@mail.gmail.com> (raw)
In-Reply-To: <ZFkkcQ2MOpku9YaF@jurong>
Hi,
On Mon, May 8, 2023 at 9:34 AM Andreas Enge <andreas@enge.fr> wrote:
>
> This does not yet explain how the branches interact with continuous
> integration.
How about requiring prior to merging a feature branch that substitutes
exist for all changed derivations? It would prevent build failures and
preempt local builds, and thereby improve the experience for average
users.
Kind regards
Felix
next prev parent reply other threads:[~2023-05-08 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168347913021.32190.10808857919894440138@vcs2.savannah.gnu.org>
[not found] ` <20230507170531.26A00C22F14@vcs2.savannah.gnu.org>
2023-05-08 1:41 ` 04/09: gnu: mesa: Update to 23.0.3 Christopher Baines
2023-05-08 12:08 ` Maxim Cournoyer
2023-05-08 12:56 ` Christopher Baines
2023-05-08 15:01 ` Maxim Cournoyer
2023-05-08 16:33 ` Feature branches (was: 04/09: gnu: mesa: Update to 23.0.3) Andreas Enge
2023-05-08 17:01 ` Feature branches Maxim Cournoyer
2023-05-10 9:21 ` Andreas Enge
2023-05-10 13:23 ` Maxim Cournoyer
2023-05-10 13:40 ` Andreas Enge
2023-05-10 13:55 ` Andreas Enge
2023-05-11 4:49 ` Maxim Cournoyer
2023-05-08 17:15 ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-05-10 9:11 ` Andreas Enge
2023-05-10 11:30 ` Christopher Baines
2023-05-08 16:39 ` 04/09: gnu: mesa: Update to 23.0.3 Christopher Baines
2023-05-09 4:37 ` John Kehayias
2023-05-09 8:39 ` Christopher Baines
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='CAFHYt56fXA0bsMPbtJWRPzifjnYVjR0afO8b_dJaXy7tK=pEAQ@mail.gmail.com' \
--to=guix-devel@gnu.org \
--cc=andreas@enge.fr \
--cc=felix.lechner@lease-up.com \
--cc=mail@cbaines.net \
--cc=maxim.cournoyer@gmail.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.
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.