From: Josselin Poiret <dev@jpoiret.xyz>
To: Leo Famulari <leo@famulari.name>
Cc: John Kehayias <john.kehayias@protonmail.com>, guix-devel@gnu.org
Subject: Re: Golang go-updates feature branch?
Date: Thu, 16 Feb 2023 21:05:42 +0100 [thread overview]
Message-ID: <87k00hs7e1.fsf@jpoiret.xyz> (raw)
In-Reply-To: <Y+5fz2itwIXMxV+j@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> Thank you for your help Josselin! It's much appreciated.
Happy to help!
> As part of our effort to move towards a "feature branch" development
> workflow, it will be useful to collect these tips so that everyone can
> create and test their own manifests and Cuirass specs.
>
> I wonder where it should go: a blog post, the cookbook, the Guix manual,
> etc?
What's the reason behind branch-specific manifests? I'd imagine we'd
want to test that Guix as a whole still works, even when upgrading just
specific parts. Otherwise, I guess this shouldn't qualify for a blog
post, maybe the cookbook but I'd even just add this as a comment at the
very top of `build-aux/cuirass/evaluate.scm`, since that's where people
will go looking for it. If it does end up becoming widespread, perhaps
a section of the manual/cookbook dedicated to how feature branches work
could be a nice home for these bits of info.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-02-16 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 19:22 Golang go-updates feature branch? Leo Famulari
2023-01-08 22:32 ` John Kehayias
2023-01-10 5:09 ` Leo Famulari
2023-02-14 21:22 ` Josselin Poiret
2023-02-16 16:54 ` Leo Famulari
2023-02-16 20:05 ` Josselin Poiret [this message]
2023-02-16 21:22 ` Leo Famulari
2023-02-17 10:27 ` Simon Tournier
2023-01-11 17:11 ` Katherine Cox-Buday
2023-01-12 1:38 ` 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=87k00hs7e1.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=leo@famulari.name \
/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.