From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id +EuMB5Dms19KEwAA0tVLHw (envelope-from ) for ; Tue, 17 Nov 2020 15:04:48 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id mG6MA5Dms18MbwAA1q6Kng (envelope-from ) for ; Tue, 17 Nov 2020 15:04:48 +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 5452A940657 for ; Tue, 17 Nov 2020 15:04:47 +0000 (UTC) Received: from localhost ([::1]:39258 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kf2XF-0003fl-6M for larch@yhetil.org; Tue, 17 Nov 2020 10:04:45 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:45282) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kf2X6-0003fP-UJ for help-guix@gnu.org; Tue, 17 Nov 2020 10:04:36 -0500 Received: from mail-wr1-x431.google.com ([2a00:1450:4864:20::431]:43495) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kf2X1-00034U-E0 for help-guix@gnu.org; Tue, 17 Nov 2020 10:04:36 -0500 Received: by mail-wr1-x431.google.com with SMTP id s8so23481967wrw.10 for ; Tue, 17 Nov 2020 07:04:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-transfer-encoding; bh=UFsP511ugg6Tx89n10B4OeQdKwPVx2As2ULDWT5R1ps=; b=lvu4245VU8XjLEtaIHeyRJpI0Nwptlvd+IBf5uBKF1HIGztgOzCxa4jEUXCgBYGB/+ ByKDorPvzSJB40ZG8fVNXs9wI2CKqBqjKgSOk0M+S+NhnX4BFTsedWHRTgqWwQCSP2EO uNIylpl10Nw8sAlDie4oZ9pma16isJrjiaKE3erBV/N49MMV0bcp6L91qtzSA55oAzu5 P+616skDpEDPa9pPREulImLBeHGwGJ6fhM8+LJ5xSmHEeZJbvJOWRO9GZWbdFBSljrdM b9vieplh6cMAoNCS/yQw4qvIvyjwMm6NHKCyiWVRpVaB13ZGxgN9pA0m6UXLCBOy/MBJ Un+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=UFsP511ugg6Tx89n10B4OeQdKwPVx2As2ULDWT5R1ps=; b=AklZWckYh9c8Y2nvJBB3ZaH58xM3IsxV+fmAC+5vSZrhGquo/vsdr/Nd0BwJVjD1J6 AhMQnGCt0IsoVAoB0/rj1TiZptKBIcCmVV81Y6WQYrr2c2HxqWdP3HBe/jRwtLuhC7YS yUSoGLhhztjKde/AsBFrxMbf7xBYuajMO93VU5p3qsmnxWnjxAFrWg3Tbi9sXFjCDsSr g7kT5SwipleqgTCs9JQVlnFbQp94w1KpVdaLhfRlIQ+QoMHi3h96Ioqi3irp8NxktJ0y wjpg6UoBhasxpOI9Vu9visBJQKKvO9qf7+agR8nhYDI66iPv1P7vork4YmhjyBpeRdhk XPIA== X-Gm-Message-State: AOAM5304vulZUYt9E15X8s3fC3EQbqCe0KM/a5Sgc42/xygcZEdZ/tTI 6sEg4SNaH/A8YhQC9eH4wIukwFKV8vfhwg== X-Google-Smtp-Source: ABdhPJzrYK2bgRmjml4PTOx/HlEqxE10MqLKIxvSIbuEJI46i4ircqG27ZVQ2yjfcTVBP0pGiMvALA== X-Received: by 2002:adf:eb47:: with SMTP id u7mr25241760wrn.163.1605625469417; Tue, 17 Nov 2020 07:04:29 -0800 (PST) Received: from lili ([2a01:e0a:59b:9120:65d2:2476:f637:db1e]) by smtp.gmail.com with ESMTPSA id m22sm29274625wrb.97.2020.11.17.07.04.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Nov 2020 07:04:28 -0800 (PST) From: zimoun To: Kyle Meyer Subject: Re: Workflow with mu4e + magit for sending patchsets to guix? In-Reply-To: <877dqkpv4t.fsf@kyleam.com> References: <87ima5f3mi.fsf@dustycloud.org> <86eeksq2v4.fsf@gmail.com> <877dqkpv4t.fsf@kyleam.com> Date: Tue, 17 Nov 2020 16:01:12 +0100 Message-ID: <86wnykni2v.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::431; envelope-from=zimon.toutoune@gmail.com; helo=mail-wr1-x431.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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: , 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=gmail.com header.s=20161025 header.b=lvu4245V; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=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: 1.09 X-TUID: eaia8VKAQjkx Hi Kyle, Thank you for the detailed explanations and hints. On Mon, 16 Nov 2020 at 21:36, Kyle Meyer wrote: >> 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). [...] > 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. To me, today the main annoyance is the selection of the patches at the step #6. For example, avoid to resend unrelated patches, as: - 000?-*.patch could resend the 0000-cover-letter.patch - *.patch could resend 0000-cover-letter.patch and 0001-Foo-bar.patch if I am currently sending v2-0001-Foo-bar.patch - any previous patchset remaining. Recent example inside my guix-artwork checkout:=20 --8<---------------cut here---------------start------------->8--- 0000-cover-letter.patch 0001-website-Add-conference-announcement.patch 0001-website-Add-fetch-methods-to-JSON-sources-and-packag.patch 0001-website-Add-integrity-to-JSON-sources.patch 0001-website-Release-conference-schedule.patch 0001-website-Update-announce-online-Guix-days.patch 0001-website-Update-manifest.patch tiny.patch v2-0001-website-Add-conference-announcement.patch v2-0001-website-Release-conference-schedule.patch v3-0001-website-Add-conference-announcement.patch v3-0001-website-Release-conference-schedule.patch v4-0001-website-Add-conference-announcement.patch v4-0001-website-Release-conference-schedule.patch --8<---------------cut here---------------end--------------->8--- That=E2=80=99s why time to time I create an output directory and put the se= ries in. But the 0000-cover-letter.patch (or vN-0000-cover-letter.patch) is still annoying because it blocks the simple *.patch. Nothing simpler than * could be done, I see you regexp integrist. :-) I am thinking loud. One option (some setq) could be added to Magit format-patch, and do under the hood: - create 0000-cover-letter.patch in the root directory - create folder v1 (default), otherwise v2 =E2=80=A6 vN and put the series in. This would be configurable via Magit variables, say: magit-send-email-workflow t magit-format-patch-directory-prefix =E2=80=9Cv=E2=80=9D =20=20 Then, the sequence, W C-m l C-m c W C-m v2 c W C-m l C-m v3 c would produce the final tree: + +- .git +- 0000-cover-letter.patch +- v3-0000-cover-letter.patch +- v1 +- 0001-Foo-Bar.patch =E2=80=A6 +- 0042-Yahoga.patch +- v2 +- v2-0001-Foo-Bar.patch =E2=80=A6 +- v2-0012-Kikool.patch +- v3 +- v3-0001-Foo-Bar.patch =E2=80=A6 +- v3-0021-Rock-and-roll.patch =20 This way, step #6 would become: !! send-email --to=3D12345@debbugs.gnu.org v1/*.patch (With or without --in-reply-to, another story. :-)) All the best, simon