unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: Re: Changes to the branching workflow
Date: Sat, 13 Feb 2021 12:19:35 +0100	[thread overview]
Message-ID: <a4e03141-7487-d028-b1d5-6cb189fdaa9b@crazy-compilers.com> (raw)
In-Reply-To: <YCWyxGmIo0v6yss+@jasmine.lan>

Am 11.02.21 um 23:42 schrieb Leo Famulari:
> The default branch names remain "core-updates" and "staging".
>
> […]
>
> During those periods, new patches can be pushed to "core-updates-next"
> and "staging-next".

What should be the use of these *-next branches. I can't see any except 
confusing committers. Why can't on push to staging and core-update 
during the active part of the cycle?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



  parent reply	other threads:[~2021-02-13 11:19 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
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 [this message]
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=a4e03141-7487-d028-b1d5-6cb189fdaa9b@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@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 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).