From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: bootstrap: i686-linux now builds without binutils, gcc seeds
Date: Mon, 17 Sep 2018 21:25:12 +0200 [thread overview]
Message-ID: <877ejk3p0n.fsf@gnu.org> (raw)
In-Reply-To: <87va743rl7.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 17 Sep 2018 20:29:40 +0200")
Ricardo Wurmus writes:
> Using Janneke’s impressive work as the beginning of core-updates-next
> sounds good to me.
Thanks!
> I’m sorry I haven’t yet been able to review wip-bootstrap myself.
As you probably saw, Ludo' is already keeping me busy and quite some
things will need some more work. Thanks for chiming in!
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-09-17 19:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 16:31 bootstrap: i686-linux now builds without binutils, gcc seeds Jan Nieuwenhuizen
2018-09-01 18:16 ` Gábor Boskovits
2018-09-02 5:21 ` Jan Nieuwenhuizen
2018-09-16 19:24 ` Ludovic Courtès
2018-09-17 6:10 ` Pjotr Prins
2018-09-17 18:29 ` Ricardo Wurmus
2018-09-17 19:25 ` Jan Nieuwenhuizen [this message]
2018-09-17 19:47 ` Jan Nieuwenhuizen
2018-09-17 21:55 ` Ricardo Wurmus
2018-09-18 8:27 ` Jan Nieuwenhuizen
2018-09-18 8:04 ` Vincent Legoll
2018-09-18 8:33 ` Jan Nieuwenhuizen
2018-09-18 20:53 ` Jan Nieuwenhuizen
2018-09-19 5:07 ` Jan Nieuwenhuizen
2018-09-19 18:07 ` Jan Nieuwenhuizen
2018-09-22 12:35 ` Ludovic Courtès
2018-09-22 15:34 ` Jan Nieuwenhuizen
2018-09-22 18:23 ` Jan Nieuwenhuizen
2018-09-23 8:02 ` branched core-updates-next [WAS: Re: bootstrap: i686-linux now builds without binutils, gcc seeds] Jan Nieuwenhuizen
2018-09-23 16:09 ` bootstrap: i686-linux now builds without binutils, gcc seeds Joshua Branson
2018-09-23 16:29 ` Jonathan Brielmaier
2018-09-22 12:23 ` Ludovic Courtès
2018-09-22 14:38 ` Jan Nieuwenhuizen
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=877ejk3p0n.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.