From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:47061) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hpbM3-0000Pg-Ip for guix-patches@gnu.org; Mon, 22 Jul 2019 12:40:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hpbM2-0005do-NL for guix-patches@gnu.org; Mon, 22 Jul 2019 12:40:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:52950) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hpbM2-0005dg-K9 for guix-patches@gnu.org; Mon, 22 Jul 2019 12:40:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hpbM2-0003KH-Cz for guix-patches@gnu.org; Mon, 22 Jul 2019 12:40:02 -0400 Subject: [bug#36555] [PATCH v3 0/3] Refactor out common behavior for system reconfiguration. Resent-Message-ID: References: <87imsci9sj.fsf@sdf.lonestar.org> <87ef30i9fl.fsf@sdf.lonestar.org> <87y3129qsn.fsf@gnu.org> <87sgr9bziq.fsf@sdf.lonestar.org> <87pnmc7nt1.fsf@gnu.org> <8736j7nwcb.fsf@sdf.lonestar.org> <87muhfjm14.fsf@gnu.org> <87ftn63l7d.fsf@sdf.lonestar.org> <87v9w1zgon.fsf_-_@sdf.lonestar.org> <87y30v3qke.fsf@sdf.lonestar.org> <87a7d924wb.fsf@dustycloud.org> <87k1caavpu.fsf@sdf.lonestar.org> From: Christopher Lemmer Webber In-reply-to: <87k1caavpu.fsf@sdf.lonestar.org> Date: Mon, 22 Jul 2019 12:39:01 -0400 Message-ID: <87muh6yqfu.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: "Jakob L. Kreuze" Cc: 36555@debbugs.gnu.org Jakob L. Kreuze writes: > Hey, Chris! > > Christopher Lemmer Webber writes: > >> My main worry is that such a patch series may be forgotten. Would it >> be inappropriate to make a "stub" patch issue for both of the followup >> patch series, since both seem important and we don't want to forget >> them? > > Alternatively, because these patches address existing issues with 'guix > deploy', should we open tickets on the issue tracker? I don't have too > much of a preference: either way should work fine for ensuring that we > don't forget about them. > > Regards, > Jakob That's a good call. Yeah, I think put them there.