From: Ricardo Wurmus <rekado@elephly.net>
To: ng0@n0.is
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: End of beta soon? drop i686?
Date: Wed, 12 Dec 2018 03:15:13 +0100 [thread overview]
Message-ID: <87d0q75w3y.fsf@elephly.net> (raw)
In-Reply-To: <20181211091944.dneczhtrave5jnjy@abyayala>
ng0@n0.is writes:
> Let's not drop an architecture because occasionally something breaks for
> it. breakage is bad, yes. but it's more than just the broken packages.
> it is the way patches find their way into master. if you have more
> patience then I had, you can try to address the workflow in guix (there
> will be some past discussions you can find on the mailinglists).
>
> I've been on the high-friction lane with GuixSD, so I am talking from
> experience and not just assumptions.
I don’t understand what you are alluding to. Could you please
elaborate? Could you translate this into concrete suggestions or
expectations?
--
Ricardo
next prev parent reply other threads:[~2018-12-12 2:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 7:58 End of beta soon? drop i686? swedebugia
2018-12-11 9:19 ` ng0
2018-12-12 2:15 ` Ricardo Wurmus [this message]
2018-12-12 9:33 ` ng0
2018-12-11 20:02 ` Mark H Weaver
2018-12-11 20:22 ` Danny Milosavljevic
2018-12-11 23:14 ` Mark H Weaver
2018-12-12 17:52 ` Mark H Weaver
2018-12-12 2:16 ` Ricardo Wurmus
2018-12-12 7:40 ` Andreas Enge
2018-12-13 12:26 ` swedebugia
2018-12-12 16:19 ` Joshua Branson
2018-12-12 23:27 ` Mark H Weaver
2018-12-12 22:33 ` George Clemmer
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 17:52 Mark H Weaver
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=87d0q75w3y.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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).