From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id QN5HHHpZOV/wEQAA0tVLHw (envelope-from ) for ; Sun, 16 Aug 2020 16:06:18 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id aMXsF3pZOV8YWwAAbx9fmQ (envelope-from ) for ; Sun, 16 Aug 2020 16:06:18 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 0FF42940715 for ; Sun, 16 Aug 2020 16:06:17 +0000 (UTC) Received: from localhost ([::1]:44762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k7LAm-0007Gm-Tw for larch@yhetil.org; Sun, 16 Aug 2020 12:06:16 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:33858) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7LAe-0007FH-2o for help-guix@gnu.org; Sun, 16 Aug 2020 12:06:08 -0400 Received: from dustycloud.org ([2600:3c02::f03c:91ff:feae:cb51]:38498) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7LAc-0007oW-DL for help-guix@gnu.org; Sun, 16 Aug 2020 12:06:07 -0400 Received: from twig (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 1F5F1265C8 for ; Sun, 16 Aug 2020 12:06:04 -0400 (EDT) User-agent: mu4e 1.4.12; emacs 26.3 From: Christopher Lemmer Webber To: help-guix@gnu.org Subject: Nicest way to send and apply Guix patchsets via magit? Date: Sun, 16 Aug 2020 12:06:03 -0400 Message-ID: <87tux2379w.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2600:3c02::f03c:91ff:feae:cb51; envelope-from=cwebber@dustycloud.org; helo=dustycloud.org X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Spam-Score: -0.01 X-TUID: 77hV19tn01H4 I know a number of developers of guix here are also Magit fans. When you have a patchset, how do you usually send it... and in the reverse direction, how do you usually go about applying a patchset? I'm going to admit awkwardly that what I've done historically is generate patches one by one and manually start a thread but it's obviously suboptimal. (I also use mu4e.) Not urgent, just wondering! There has to be a better way than what I've done. ;)