From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Re: Rust team branch
Date: Thu, 16 Feb 2023 11:56:16 +0100 [thread overview]
Message-ID: <Y+4L0IEHKO+63IQm@jurong> (raw)
In-Reply-To: <Y+vp8L2PP38wkTgQ@3900XT>
Am Tue, Feb 14, 2023 at 10:07:12PM +0200 schrieb Efraim Flashner:
> > By "pull out" you mean revert them in staging and apply them on a separate
> > branch? That would also delay #61475 and maybe ease merging of the staging
> > branch.
> I was thinking more of cherry-picking them into a branch, not
> necessarily reverting them on staging.
Okay. But it would be nice then to revert at least as much in staging
that the branch builds and can be merged.
Andreas
next prev parent reply other threads:[~2023-02-16 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 12:19 Discussion notes on releases and branches Andreas Enge
2023-02-12 21:13 ` Moving forward with teams and feature branches (was: Discussion notes on releases and branches) Josselin Poiret
2023-02-12 21:34 ` Andreas Enge
2023-02-13 9:32 ` Time for RFC? (was Re: Moving forward with teams and feature branches (was: Discussion notes on releases and branches)) zimoun
2023-02-13 14:04 ` bug#61475: Staging branch (was: Moving forward with teams and feature branches) Andreas Enge
2023-05-10 2:55 ` Maxim Cournoyer
2023-02-13 14:07 ` Moving forward with teams and feature branches (was: Discussion notes on releases and branches) Andreas Enge
2023-02-14 19:12 ` Leo Famulari
2023-02-13 9:22 ` Release (was " Simon Tournier
2023-02-14 10:14 ` Rust team branch " Efraim Flashner
2023-02-14 16:36 ` Rust team branch Andreas Enge
2023-02-14 20:07 ` Efraim Flashner
2023-02-16 10:56 ` Andreas Enge [this message]
2023-02-14 16:36 ` Rust team branch (was Re: Discussion notes on releases and branches) Katherine Cox-Buday
2023-02-14 20:08 ` Efraim Flashner
2023-02-15 17:49 ` Katherine Cox-Buday
2023-03-17 15:24 ` Discussion notes on releases and branches Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-18 17:42 ` 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=Y+4L0IEHKO+63IQm@jurong \
--to=andreas@enge.fr \
--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 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.