From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: More stability needed in our Rust packages, for IceCat 60
Date: Sat, 22 Sep 2018 14:20:15 -0400 [thread overview]
Message-ID: <877ejde6n4.fsf@netris.org> (raw)
In-Reply-To: <20180922104101.5c9e2a57@scratchpost.org> (Danny Milosavljevic's message of "Sat, 22 Sep 2018 10:41:01 +0200")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> writes:
>> How would you feel about doing further Rust work on a separate branch,
>> and periodically (maybe 2-4 times per month) merging the collected
>> improvements into master?
>
> I agree actually. Rust is taking up way too much of my own build
> capacity right now. Even small changes have to be tested on at least
> a few of the compilers, because Rust seems to change what settings one
> can use regularily - and any of those could break master (and did before).
>
> I've reverted the last commit mentioning "ar". It's not strictly the
> right fix to revert it, but it's the most stable version to have on
> master.
>
> I've also been talking to a new volunteer, so now is actually a good
> time for oponeing a new branch.
>
> I've now opened wip-rust and will be pushing it after some rust versions
> built.
Sounds good. Thanks again!
Mark
next prev parent reply other threads:[~2018-09-23 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180921155929.16408.29671@vcs0.savannah.gnu.org>
[not found] ` <20180921155930.0EB7B20498@vcs0.savannah.gnu.org>
2018-09-22 3:35 ` More stability needed in our Rust packages, for IceCat 60 Mark H Weaver
2018-09-22 7:11 ` Pjotr Prins
2018-09-22 8:47 ` Danny Milosavljevic
2018-09-22 8:41 ` Danny Milosavljevic
2018-09-22 14:48 ` Joshua Branson
2018-09-24 8:36 ` Clément Lassieur
2018-09-24 14:13 ` Joshua Branson
2018-09-22 18:20 ` Mark H Weaver [this message]
2018-09-23 13:25 ` Ludovic Courtès
2018-09-23 1:22 ` Mike Gerwitz
2018-09-24 8:38 ` Clément Lassieur
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=877ejde6n4.fsf@netris.org \
--to=mhw@netris.org \
--cc=dannym@scratchpost.org \
--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).