From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id MFC1ENbm2GMHIyYAWB0awg (envelope-from ) for ; Tue, 31 Jan 2023 05:00:54 -0500 Received: by simark.ca (Postfix, from userid 112) id 4103F1E128; Tue, 31 Jan 2023 05:00:54 -0500 (EST) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=PoalXFTR; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id EB67D1E110 for ; Tue, 31 Jan 2023 05:00:53 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 3B48A385841E for ; Tue, 31 Jan 2023 10:00:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3B48A385841E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675159252; bh=2NToHWkPIVOQgxIrmrA57ag7kuS5xlDzDvRzoF+VSKI=; h=Date:To:Cc:Subject:References:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=PoalXFTRJKKxBo2/Q9rRD7ZDa0YpON0dCEmSEwdGm0Lm2kEH64SokD5Igg11KYfnm 2b3CI1LuVROXwuURj978u4ktTxXvycGPwpp78tygQ09N7ZkRyU46K+yB3KBlagOsoe iLJg9zqlXSzU8Hol2MC4lqOO1L2AnMPPqguwZRd8= Received: from lndn.lancelotsix.com (lndn.lancelotsix.com [51.195.220.111]) by sourceware.org (Postfix) with ESMTPS id 2483A3858D28 for ; Tue, 31 Jan 2023 10:00:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2483A3858D28 Received: from ubuntu.lan (unknown [IPv6:2a02:390:9086::146]) by lndn.lancelotsix.com (Postfix) with ESMTPSA id 6EECE80E9E; Tue, 31 Jan 2023 10:00:22 +0000 (UTC) Date: Tue, 31 Jan 2023 10:00:10 +0000 To: Mark Wielaard Cc: Tom Tromey , Luis Machado , Simon Marchi , "gdb@sourceware.org" , John Baldwin Subject: Re: Any concrete plans after the GDB BoF? Message-ID: <20230131100010.bmohnw3yrd4igjpw@ubuntu.lan> References: <83485199-965e-7ff5-1dc8-d027b74b56f7@arm.com> <20230101220250.GA11041@gnu.wildebeest.org> <87tu0lxgee.fsf@tromey.com> <87bkmtx83b.fsf@tromey.com> <20230127155016.zchm4tsawlkdfyne@ubuntu.lan> <87mt63ilkm.fsf@tromey.com> <20230130174318.m2itnzacnbbtxdl6@ubuntu.lan> <20230130184651.GG11361@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230130184651.GG11361@gnu.wildebeest.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (lndn.lancelotsix.com [0.0.0.0]); Tue, 31 Jan 2023 10:00:22 +0000 (UTC) X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Lancelot SIX via Gdb Reply-To: Lancelot SIX Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" > b4 acts a little different from git-pw. It uses Message-IDs to fetch > patches (and/or a whole thread as mbox). So it helps if your mta > displays those prominently. If you use emacs you might be interested > in piem: https://git.kyleam.com/piem/about/ > > For gdb-patches you want to add the following to your .git/config: > > [b4] > midmask = https://inbox.sourceware.org/gdb-patches/%s > linkmask = https://inbox.sourceware.org.org/gdb-patches/%s > > There is a command line example in this presentation: > https://gnu.wildebeest.org/~mark/fsf-sourceware/presentation.html#slide14 > > The latest b4 can also interact with patchwork, but I haven't tried > that out yet. The new settings are described at: > https://b4.docs.kernel.org/en/latest/config.html#patchwork-integration-settings > Thanks for the pointers! I usually use mutt, so having the message id shown is quite easy (if it can help someone, I have "unignore Message-Id:" in my muttrc file). I'll play around with this, it might fit slightly better in my workflow than git-pw. Best, Lancelot.