From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Changes to the branching workflow
Date: Fri, 12 Feb 2021 20:34:34 +0100 [thread overview]
Message-ID: <877dndcc6t.fsf@nckx> (raw)
In-Reply-To: <YCbCYFXPQK9+fzMY@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Hi Leo!
Leo Famulari 写道：
> I thought that the use of -frozen and -next might help avoid
> mistakes
> during the active part of the cycles.
Ah, there's my blind spot. What kinds of mistakes? When is it
harmful to push to the open branch?
I say ‘the open branch’ because core-updates and core-updates-next
are the same thing, constantly changing its name in perfect
(manual!) sync with -frozen & I don't understand why (yet). Seems
obscure & error prone.
> If someone wasn't aware of the branch status, the lack of a
> 'core-updates' branch might make them think twice and ask for
> advice.
I think they'll push and create a third one. I won't blame them.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-02-12 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 22:42 Changes to the branching workflow Leo Famulari
2021-02-12 10:34 ` Tobias Geerinckx-Rice
2021-02-12 18:01 ` Leo Famulari
2021-02-12 19:34 ` Tobias Geerinckx-Rice [this message]
2021-02-12 20:17 ` Leo Famulari
2021-02-12 20:49 ` Andreas Enge
2021-02-13 11:24 ` Hartmut Goebel
2021-02-13 18:21 ` Leo Famulari
2021-02-13 19:40 ` Tobias Geerinckx-Rice
2021-02-13 11:19 ` Hartmut Goebel
2021-03-04 21:05 ` Christopher Lemmer Webber
2021-03-04 22:01 ` zimoun
2021-03-05 15:34 ` Christopher Lemmer Webber
2021-03-05 15:52 ` 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
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=877dndcc6t.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--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 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).