From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Andreas Enge <andreas@enge.fr>, guix-devel@gnu.org
Subject: Re: Rust team branch (was Re: Discussion notes on releases and branches)
Date: Wed, 15 Feb 2023 10:49:17 -0700 [thread overview]
Message-ID: <360ca0e4-de17-09d5-6b7e-31d532987eff@gmail.com> (raw)
In-Reply-To: <Y+vqPjCc8SmcN1oj@3900XT>
On 2/14/23 1:08 PM, Efraim Flashner wrote:
> Also I don't think there's a lot of overlap between go and rust so we
> can probably have both going at the same time.
Oh, yes, I didn't mean to imply that the two were related, or
conflicted. I just wanted to point it out in case it was of any help.
Best of luck to the rust team!
--
Katherine
next prev parent reply other threads:[~2023-02-15 17:49 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
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 [this message]
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=360ca0e4-de17-09d5-6b7e-31d532987eff@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=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.