From: Christopher Baines <mail@cbaines.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release 1.2.1: status
Date: Fri, 19 Mar 2021 08:27:07 +0000 [thread overview]
Message-ID: <87ft0rczvo.fsf@cbaines.net> (raw)
In-Reply-To: <875z1n1wfb.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Chris Marusich <cmmarusich@gmail.com> writes:
> Hi simon,
>
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> First, thanks to Chris and folks, powerpc64le-linux will be [1] in the
>> next release, great! Isn’t it? :-)
>
> I'm very excited about this! Efraim was able to rework our patches so
> they could be applied to master without rebuilding the entire world.
> The patches are currently under review here:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47182
>
> More review is welcome, but unless some unforeseen issues are
> discovered, I agree that we can go ahead with adding support for
> powerpc64le-linux.
>
> Where is the release work happening? Where can I merge or apply these
> changes to ensure they get included in the next release?
In the past, a branch might appear for the release, but that hasn't
happened yet. Merging to master is the next step I believe, and as you
say, I think the patches are ready.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2021-03-19 8:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 14:28 Release 1.2.1: status zimoun
2021-03-19 6:37 ` Chris Marusich
2021-03-19 8:27 ` Christopher Baines [this message]
2021-03-19 8:50 ` zimoun
2021-03-20 18:09 ` Leo Famulari
2021-03-20 22:56 ` zimoun
2021-03-20 23:21 ` Leo Famulari
2021-03-19 18:31 ` Andreas Enge
2021-03-19 21:59 ` Luis Felipe
2021-03-20 23:03 ` zimoun
2021-03-19 22:26 ` Luis Felipe
2021-03-21 0:16 ` zimoun
2021-03-21 14:13 ` Luis Felipe
2021-03-20 20:01 ` Leo Famulari
2021-03-20 23:00 ` zimoun
2021-03-21 17:54 ` 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
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=87ft0rczvo.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=cmmarusich@gmail.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).