From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id GVMmHYQ6s18zDgAA0tVLHw (envelope-from ) for ; Tue, 17 Nov 2020 02:50:44 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id 8HCkGIQ6s18JXwAAB5/wlQ (envelope-from ) for ; Tue, 17 Nov 2020 02:50:44 +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 6E6229404C7 for ; Tue, 17 Nov 2020 02:50:43 +0000 (UTC) Received: from localhost ([::1]:37900 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ker4r-0002Rj-Ah for larch@yhetil.org; Mon, 16 Nov 2020 21:50:41 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:58746) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keqr3-0001bz-D5 for help-guix@gnu.org; Mon, 16 Nov 2020 21:36:25 -0500 Received: from pb-smtp1.pobox.com ([64.147.108.70]:58211) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1keqr0-0002AD-Ch for help-guix@gnu.org; Mon, 16 Nov 2020 21:36:24 -0500 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id CA9808B036; Mon, 16 Nov 2020 21:36:19 -0500 (EST) (envelope-from kyle@kyleam.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:in-reply-to:references:date:message-id:mime-version :content-type:content-transfer-encoding; s=sasl; bh=i4MA4nAFzc/o N7GlAHBPZUOxqoU=; b=DsBhzAdDtLVoM2nyIXM4uUGE69eU33nSQn8BUKkywECA U/iDaUA5Z30W3mvxw9UKJSxpUJXsSdi18hGKubcC4do+hClslxcUBoDgt6Sefvge W79SMFZ8/cWgoLb2aRLUF5OpM3Uexc4SIEjYcRBfFEkcyev5XpV2WtOOj9r+6Es= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id AE1988B034; Mon, 16 Nov 2020 21:36:19 -0500 (EST) (envelope-from kyle@kyleam.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kyleam.com; h=from:to:cc:subject:in-reply-to:references:date:message-id:mime-version:content-type:content-transfer-encoding; s=mesmtp; bh=4FyDFbYq3r7jRrEaUWTyNgxZdPXUzs/TPJmYMiuIjYY=; b=kLjO83JLEmokX4NVwJzHrwKWx53tWvc47tJxAJDvDJIT7StgFTfYz3+/h3/Ct33WRKVxzb3oFDKd7uzilSCHPc7eSYd0fnh/h9Z5QAaHfdRbeC6i428BW+qqLzeYlbV/xgvcMSEIGht+Eb9Z+4N1S0qb0HK8EDsovj2drtKQVDY= Received: from localhost (unknown [45.33.91.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 1E7798B033; Mon, 16 Nov 2020 21:36:19 -0500 (EST) (envelope-from kyle@kyleam.com) From: Kyle Meyer To: zimoun Subject: Re: Workflow with mu4e + magit for sending patchsets to guix? In-Reply-To: <86eeksq2v4.fsf@gmail.com> References: <87ima5f3mi.fsf@dustycloud.org> <86eeksq2v4.fsf@gmail.com> Date: Mon, 16 Nov 2020 21:36:18 -0500 Message-ID: <877dqkpv4t.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Pobox-Relay-ID: AC487F94-287D-11EB-846A-D152C8D8090B-24757444!pb-smtp1.pobox.com Received-SPF: pass client-ip=64.147.108.70; envelope-from=kyle@kyleam.com; helo=pb-smtp1.pobox.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/16 21:36:20 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 16 Nov 2020 21:50:30 -0500 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: , Cc: help-guix@gnu.org Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=fail (headers rsa verify failed) header.d=pobox.com header.s=sasl header.b=DsBhzAdD; dkim=fail (headers rsa verify failed) header.d=kyleam.com header.s=mesmtp header.b=kLjO83JL; 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.99 X-TUID: psYowBeaLswU zimoun writes: > Hi Chris > > +CC Kyle since they probably knows the status [1]. Sorry, I have no good news for you :/ > On Mon, 16 Nov 2020 at 15:28, Christopher Lemmer Webber wrote: > >> I've been making patchset series of emails to guix-patches manually. >> I'm sure this is the wrong thing to do. I use mu4e + magit and know >> others have a similar setup. >> >> What do you all do? > > I am sending really few patches so my workflow is probably not > optimized. What I do is from magit-status: > > 1. Select the commits I'd suggest always setting an upstream for topic branches. Then the range you're interested in is almost always "@{upstream}.." (which can be shortened to "@{u}.."). Or you can add something like this to Magit's popup [1]: ;; https://git.kyleam.com/emacs.d/tree/lisp/km-magit.el?id=3D928629a9ccd8= b439d0e98d9976b75c4cf5f048f9#n836 (defun km/magit-patch-create-from-upstream (&optional args) (interactive (list (transient-args 'magit-patch-create))) (if-let ((upstream (magit-get-upstream-branch))) (apply #'magit-run-git "format-patch" upstream args) (user-error "No upstream branch"))) (transient-append-suffix 'magit-patch-create "c" '("u" "@{upstream}.." km/magit-patch-create-from-upstream)) Most of my magit customizations never find their way upstream (they tend to be very tailored to me), but something like the command above would probably be good to add. > 2. W c > C-m b origin/master RET Yay, base commit :) Note that with the upstream set, you can select "auto" here. Or you can configure format.useAutoBase to "whenAble" and not bother setting the option for each invocation. > C-m l If you follow the convention of writing a cover letter only for multi-patch series, you can drop the 'C-m l' because by default git will generate a cover letter when there is more than one commit. > c > 3. Edit the cover letter > 4. !! send-email --to=3Dguix-patches@gnu.org 0000-cover-letter.patch > 5. Wait and refresh my inbox > 6. !! send-email --to=3D12345@gnu.org 000?-*.patch Yeah, 4-6 are tricky and debbugs-specific. For other projects, it could just be 'send-email *.patch' once sendemail.to is configured to point to the list's address. For 6, using '--no-thread --in-reply-to=3D...' will retain the same threading you'd see if you weren't using debbugs (i.e didn't have to do the two-step send). Also, not helpful for mu4e users, but since I know simon uses notmuch... notmuch has a really handy notmuch-show-stash-git-send-email. I have a variant for step 5 above. If you call it visiting the acknowledgment message, it will copy --to=3D"NNNNN@debbugs.gnu.org" --in-reply-to=3D"message-id" to your kill ring. https://git.kyleam.com/emacs.d/tree/lisp/km-mail.el?id=3D928629a9ccd8b439= d0e98d9976b75c4cf5f048f9#n225 > AFAIK, there is no =E2=80=99send-email=E2=80=99 support with Magit. [...] > > What I have understood is that Magit-forge should implement =E2=80=99send= -email=E2=80=99 > as a backend (forge) but it has not happened yet. Or I missed the > news. :-) Right, there's no send-email support in Magit (or any of the extensions under its organization). I of course can't speak for Jonas, but I'm not aware of any movement or concrete plans on that front. I think the most recent thread to touch on this is actually the one you opened early this year about extending format-patch options: . And, sadly I guess, my view is still similar to what I said there: send-email has of course come up a number of times before (gh-1756 and gh-1800 are the most relevant, I think), and tackling that requires a vision that I don't really have. Perhaps due to a lack of imagination, I can't think of an implementation on Magit's side that would improve the simple send-email command that I run. In terms of sending mail, the most involved thing that I need to do is get the --to/--ccs and --in-reply-to from an existing thread, but in my view that's outside of Magit's scope. I don't know. Maybe I should try to think harder about it. A final note of hope: as a lurker on the notmuch list, I've noticed that Jonas has starting doing some patch-based contributions. So, perhaps he'll get an itch and do his amazing Jonas thing.