From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id gHyoBSw/xGXPDwEA62LTzQ:P1 (envelope-from ) for ; Thu, 08 Feb 2024 03:40:44 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id gHyoBSw/xGXPDwEA62LTzQ (envelope-from ) for ; Thu, 08 Feb 2024 03:40:44 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=kyleam.com header.s=key1 header.b=NPd1As66; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1707360044; a=rsa-sha256; cv=none; b=PTUvRlqcG569gXKEmI49bH6equNgeIZtunt403ILhAhXaLiubJL5LStjxjxxeeSFN1Jziw dajigseMX7R4J1klVDGAgZHetBnGX4yHwIQGEuxyQhQu0qTCMqkp2ew8in/CZKTnc7zrIc kDiwcBVL0qhqJ1/AH4xYuQ9aYl3U5vt+YwIS1dWagXtY5ZXg0NOz76UlmT72PKGH83sNIz 1n6JPOczDFryHQeqJU0iIxShLeW8roJK25cL0u6OCt2fMLu8UVGAt3YxcVijV8Tn01Zj1y 3VAOGOshmUVmdFMwSow6JqV8lQNP2HFTUKIu8DiG5fpbia1xENN49bcdUYlEXQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=kyleam.com header.s=key1 header.b=NPd1As66; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1707360044; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=MQyfxQv/prhuoUEsoruzdKdGQ551gpEsLMJ/qhf5bPQ=; b=rriifbAbxeJChlDe1v4TTjWS5/GrZngVu++/ZWsB2TtCj9D4LZdXgc+Pz3CGsLPMPvxS3h 3m7oMJyNJq/24v/DbBnK/GKIfZAfrQ27m0Hbr+Q02ig1+PR8EQinH2c8aWMjZY2nftPaoz ERts8MWAqOeJMeHpQzSgTLNmXdvHFcljQ1Qu6A93S5up0D1lwIrmhRsrrvihU9RtRHqYsJ cVuPD6dAni5X0rg+wMo4FubA8O/dUZ1Y5m/Gb2O4g9z6wlpKP264OxAyGx+JH+FEKoNCA0 8TMo2bxY/Lv4E2zCj9BVEXXvQd8jRqHLzmRKQcDBdRQeqYH2KflViF+hh8FBlg== 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 0148C7F0DD for ; Thu, 8 Feb 2024 03:40:44 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rXuKQ-00078b-EA; Wed, 07 Feb 2024 21:39:54 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rXuKP-00078S-NZ for guix-devel@gnu.org; Wed, 07 Feb 2024 21:39:53 -0500 Received: from out-170.mta1.migadu.com ([2001:41d0:203:375::aa]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rXuKM-0008FT-Rc for guix-devel@gnu.org; Wed, 07 Feb 2024 21:39:53 -0500 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1707359980; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MQyfxQv/prhuoUEsoruzdKdGQ551gpEsLMJ/qhf5bPQ=; b=NPd1As669Pq0N19bl7mIXugJW5Q/5ikTto2MOfVTiusJTEpVtPKORxFVNrpY7d9MjytlyX biG+PQ6et/h99ndIZfmcHJSf8aBtwIaSbpbDLft3ySr4fKjRMQbKnapm7ZHEJWhnkKjrrL yJp1x3ibP3GJKO9s66dv/tIhoNmNFjx0QTz/6tuTQVFx9/Qe+bP8iTQY0RcSPHZJ3m8q26 8pGtxhPFWZ1ddqFsX0mqgW+kq5EoUcJY28VOnz9RNbH5/IniBO89NO7O8P/JvVBlqA+VLq 6C7igl/iOwmvOIPPgLYujcf/iC/J5gIvSlqdDo8NSpTEcAEBL07tdRj3zPcHMQ== From: Kyle Meyer To: Ricardo Wurmus Cc: Josselin Poiret , Hartmut Goebel , Suhail , guix-devel@gnu.org Subject: Re: Guix Days: Patch flow discussion In-Reply-To: <87bk8s58p1.fsf@elephly.net> References: <87plx8fl2a.fsf@jpoiret.xyz> <87bk8s58p1.fsf@elephly.net> Date: Wed, 07 Feb 2024 21:39:35 -0500 Message-ID: <87y1bv1xy0.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2001:41d0:203:375::aa; envelope-from=kyle@kyleam.com; helo=out-170.mta1.migadu.com 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list 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+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx10.migadu.com X-Spam-Score: -7.37 X-Migadu-Queue-Id: 0148C7F0DD X-Migadu-Spam-Score: -7.37 X-TUID: 587P5lu9nz/R Hi Ricardo, Ricardo Wurmus writes: > Hi Josselin, >> They both can co-exist with debbugs, and for now the patchwork instance >> of QA is not usable for status tracking (because it is not meant to be >> used as such for now). One can already use both of them, but using both >> supercedes debbugs, and gets rid of its limitations. I've been using >> b4/lei with the yhetil public-inbox instance, with piem.el as an >> interface, and it's really useful. With a properly configured b4, one >> could simply run `b4 shazam some-msg-id` and it would automatically >> apply the corresponding patchset. > > I=E2=80=99m interested in adopting this workflow. Where can I find more > information on how to configure this? In 889a6204f8 (doc: Add some guidelines for reviewing, 2023-11-07), Maxim added some b4 configuration to Guix's etc/git/gitconfig that points at yhetil.org. With that setup, running 'b4 shazam MESSAGE-ID' from a Guix checkout should work. You may have just be asking about configuring 'b4 shazam', but if you (or others) are interested in configuring piem, read on :) piem setup and use =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D For piem, you need some custom setup in your Emacs config. https://docs.kyleam.com/piem/Registering-inboxes.html piem-inboxes contains entries that provide info to help piem map from a message (say in Notmuch or Gnus) to a public-inbox URL and to a local checkout of the repo. (setq piem-inboxes '(("guix" :coderepo "/path/to/your/clone/of/guix/" :url "https://yhetil.org/guix/" :listid "bug-guix.gnu.org"))) Further setup depends on how (in Emacs) you read your messages. https://docs.kyleam.com/piem/Enabling-integration-libraries.html For example, a Notmuch user would enable piem-notmuch-mode: (piem-notmuch-mode 1) Or a debbugs.el user would enable piem-debbugs-mode (contributed by Jelle Licht). You can enable more than one integration library. Once that's set up, the main entry point to b4 is the piem-b4-am transient. That transient in turn has the main command of interest, piem-b4-am-from-mid. https://docs.kyleam.com/piem/Using-b4-to-apply-patches.html Calling piem-b4-am-from-mid from, say, a Notmuch message with a patch series will prepare the "am-ready" series, prompt you for the name of a branch to create, and apply the series with 'git am' to the configured repo. piem-b4-am-from-mid vs b4 shazam =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D piem-b4-am-from-mid (from Emacs) and 'b4 shazam' (from the shell visiting Guix repo) are similar in spirit: use 'b4 am' to prepare an am-ready mbox from a thread's full mbox and then use 'git am' apply it to a repo. A key difference is that, with piem, you start off in some non-repository Emacs buffer containing a message and then piem knows how to get to the repository (using the config above). As a side note: 'b4 shazam' didn't exist when I wrote piem's b4 integration. At some point, I plan to add 'b4 shazam' support to piem, similar to how there is a piem command (piem-b4-am-ready-from-mid) that's a direct interface to 'b4 am', without the extra handling of piem-b4-am-from-mid. This will allow callers that prefer to use shazam invoke it from Emacs rather than the command line. lei =3D=3D=3D There's also mention upthread of lei. I don't think you're asking about configuring that, but fwiw that's public-inbox's local command-line client. I gave a short (and incomplete) description of it here: https://yhetil.org/guix-devel/87a6izsoio.fsf@kyleam.com piem currently has some basic support for lei, focused on searching public-inbox instances and displaying the results in Emacs.