unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: I've rebased wip-ppc64le onto core-updates
Date: Wed, 10 Mar 2021 12:37:28 +0200	[thread overview]
Message-ID: <YEihaMYGn0n9k0gS@3900XT> (raw)
In-Reply-To: <87czw75n4x.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

On Wed, Mar 10, 2021 at 11:17:02AM +0100, Ludovic Courtès wrote:
> Hi Chris,
> 
> Chris Marusich <cmmarusich@gmail.com> skribis:
> 
> > I just wanted to let you know that I've rebased the wip-ppc64le branch
> > onto core-updates.  The wip-ppc64le branch head used to be
> > 147b74817e6cf97f37090ecfd52e2588f4c39f7e, but now it's
> > df5d633db7acf6389ca9d444b8f5784a0da5ac5d.
> >
> > I wanted to inform you so you don't get caught off-guard the next time
> > you update your local copy.
> >
> > I've squished some commits together where it made sense to do so.  I've
> > omitted some commits which were cherry-picked before, but which are
> > already in the core-updates branch.  And I have explicitly NOT merged
> > master into wip-ppc64le at this time.
> 
> Noted.
> 
> > I have also taken the liberty of cherry-picking Tobias' commit
> > 65fb3a3eb9a759e3dba18e78113e80d7e5b353f4 from master, which adds Léo to
> > .guix-authorizations.  This should allow him to add commits on
> > wip-ppc64le without worrying about causing problems for "guix pull"
> > later.
> 
> Good idea.
> 
> We’ll have to think about merging.  At things stand, it seems that the
> bits that could go to ‘master’ (those that don’t trigger a world
> rebuild) are already there, right?
> 
> For the rest, we could aim for rebasing on core-updates and merging
> there.
> 
> WDYT?

As noted in another thread this would involve updating gcc to gcc-8.
There are some other patches which could go straight into master (I'm
looking at libelf specifically, probably others), but glibc and
gcc/libstdc++ I'm not sure how to do those ones.

Actually, looking at the branch there's also findutils-boot0, but that
can be changed to only be for target-powerpc for now and changed in
core-updates. I have a similar one I had to do for binutils on
powerpc-linux that I managed to make not affect other architectures.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-03-10 10:39 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28  6:53 I've rebased wip-ppc64le onto core-updates Chris Marusich
2021-02-28 20:42 ` Léo Le Bouter
2021-03-01 19:14   ` Tobias Platen
2021-03-01 21:36   ` jbranso
2021-03-10 10:17 ` Ludovic Courtès
2021-03-10 10:37   ` Efraim Flashner [this message]
2021-03-11  8:24   ` Chris Marusich
2021-03-11  8:37     ` Léo Le Bouter
2021-03-15 16:25     ` Ludovic Courtès
2021-03-16  4:26       ` I've rebased wip-ppc64le onto core-updates, Re: Release on April 18th? Chris Marusich
  -- strict thread matches above, loose matches on Subject: below --
2021-03-02 14:51 zimoun
2021-03-02 16:00 ` Julien Lepiller
2021-03-02 20:03 ` Leo Famulari
2021-03-05 14:31   ` Andreas Enge
2021-03-05 19:27     ` Leo Famulari
2021-03-05 20:20       ` zimoun
2021-03-05 20:58         ` Leo Famulari
2021-03-05 23:57           ` zimoun
2021-03-06 20:14           ` Tobias Geerinckx-Rice
2021-03-03 14:16 ` Ludovic Courtès
2021-03-03 18:51   ` Leo Famulari
2021-03-04  9:41     ` zimoun
2021-03-04 19:07       ` Leo Famulari
2021-03-04 22:18         ` zimoun
2021-03-04 22:43           ` Leo Famulari
2021-03-05 20:19     ` Leo Famulari
2021-03-05 23:58       ` zimoun
2021-03-06 18:56         ` Leo Famulari
2021-03-06 19:06     ` Leo Famulari
2021-03-06 23:22       ` Leo Famulari
2021-03-07  3:51         ` Raghav Gururajan
2021-03-07  5:39           ` Raghav Gururajan
2021-03-07 20:44             ` Leo Famulari
2021-03-07 20:56               ` Raghav Gururajan
2021-03-07 20:50             ` Leo Famulari
2021-03-08  9:38       ` zimoun
2021-03-05 20:21   ` Leo Famulari
2021-03-09 18:17 ` Chris Marusich
2021-03-09 21:32   ` Vincent Legoll
2021-03-10  8:30     ` Release on April 18th? (ppc64le support specifically) Efraim Flashner
2021-03-11  9:10     ` Release on April 18th? Chris Marusich
2021-03-12  8:02       ` Vincent Legoll
2021-03-12 18:42         ` Chris Marusich
2021-03-12 18:52           ` Chris Marusich
2021-03-14 12:31           ` Vincent Legoll
2021-03-15 16:36           ` Ludovic Courtès
2021-03-16  4:03           ` Let's include powerpc64le-linux in the next release (was: Re: Release on April 18th?) Chris Marusich
2021-03-16  7:08             ` Efraim Flashner
2021-03-16  8:10               ` Léo Le Bouter
2021-03-23 13:42             ` Let's include powerpc64le-linux in the next release Ludovic Courtès
2021-03-23 13:47               ` Léo Le Bouter
2021-03-23 14:01               ` Tobias Geerinckx-Rice
2021-03-30  8:23                 ` Ludovic Courtès
2021-03-30 22:20                   ` Vincent Legoll
2021-03-23 17:09               ` Let's include powerpc64le-linux in the next release, " Chris Marusich
2021-03-10 13:27   ` Release on April 18th? zimoun
2021-03-10 15:30     ` Efraim Flashner
2021-03-10 15:59       ` zimoun
2021-03-10 18:33         ` Efraim Flashner
2021-03-11  8:58       ` Chris Marusich
2021-03-11 13:30         ` Efraim Flashner
2021-03-12  8:33           ` Chris Marusich
2021-03-12 10:11             ` Andreas Enge
2021-03-12 13:43             ` Efraim Flashner

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=YEihaMYGn0n9k0gS@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).