From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Lirzin Subject: Re: [PATCH] vm: Have qemu-image generate derivations instead. Date: Tue, 12 Apr 2016 02:01:27 +0200 Message-ID: <87shyrsnjc.fsf@gnu.org> References: <56c321ad.e4f9420a.ee59b.4aa7@mx.google.com> <87h9fphxtl.fsf@gnu.org> <20160329231340.GA13977@jookia-eeepc.Home> <20160411222153.GA9461@novena-choice-citizen.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1apllw-0005XN-BU for guix-devel@gnu.org; Mon, 11 Apr 2016 20:01:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1apllv-0003TQ-Ft for guix-devel@gnu.org; Mon, 11 Apr 2016 20:01:36 -0400 In-Reply-To: <20160411222153.GA9461@novena-choice-citizen.lan> (Jookia's message of "Tue, 12 Apr 2016 08:21:53 +1000") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jookia <166291@gmail.com> Cc: guix-devel@gnu.org Hello, Jookia <166291@gmail.com> writes: > I'm hesitant to write this email so I'll make it quick: > > I'm withdrawing from submitting this patch and all others of mine such as proxy > support and Libreboot support. Too bad. :( > The process of getting changes reviewed and incorporated in to > upstream isn't suited for me, the tooling just isn't there yet and > participating in IRC makes me sad. What doesn't suits you? IME Guix is a welcoming community, so I think you can speak freely about things that you think are not working well without expecting aggressive reaction. So if you feel up to, please don't make it "quick". Taking a look at this thread, I have seen that you didn't get quick answers. If this is the main problem then pinging the thread regularly (once a week for example) is not considered bad behavior. > I'm going to just create a downstream fork of Guix somewhere with > those features and put my patches there without worrying too much. If > something's really needed, someone else can upstream it. if waiting for patch reviews blocks you in your workflow, this could perhaps work better. However if you choose this path please take some time to follow Guix coding style (indentation + changelog style commits) and notify the list when you achieve something. It would help things to get merged then. -- Mathieu Lirzin