From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 09B75276051; Wed, 10 Sep 2025 12:19:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757506794; cv=none; b=ICSxg5fmdAeXIIjj7gXkAF2a0e7O+G73paiCYJMfRqs5Ry2rCVRzHmw0nOW6ClbDFI3gD7TdGcQ+50ek+aWagQlm9BN09HgE4Iwu890C5VGFBZAjjqZuFoVnfs1BnGMj6Wfh9twrRK359+nHj/JxtKrNgVwUYOMWoOhhdQo46HM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757506794; c=relaxed/simple; bh=m2lIjYXiBT84ffpnStHjjrdVAEucnB8L201CVsqOcpQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=nyizJ3DP5n4pt45wL61/PGnRJIjtzBpygAVkSTI2kwS3gc3nHHjBT6nftDXe3LCBl1cQf/P/aRQHwB3X4PnIIlUqUuOzYiIT+rAaVq88Cdvh19pnLTI7NyZVGeaaE1kOCy28blLAwko7r2GzgccHIUhehkTwA0fTN6Q0AJIDUag= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=P1fwqZZb; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="P1fwqZZb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A22EBC4CEF0; Wed, 10 Sep 2025 12:19:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1757506793; bh=m2lIjYXiBT84ffpnStHjjrdVAEucnB8L201CVsqOcpQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=P1fwqZZblkaa++z0wFf2WXhuT6pgQBQ22dAKJ2qpqVgL6AxKY9XofdpsYdjbhCQJW uTdSCDeKrlAyStGzYZNNwMB3PBPVpvW019gqa4t3tWw42ZaTtqTKxTYHYVYyLVs3OA euImLd9U2hXfdgSysMva40iyuZn5smrLakqk9XJW6TEY7/GwQKeIe6XgRUJBBuYTmI alazqy3BYePzNnpMRNsXstYllJVq6xUDvsO8dWQ1JYwIE/dF1MuslVqUFEve+fUEgn Ro1ku1TkY5izDiaMpr++NyIYizAtaJqUCkbFmhuBuMwA5If4hUyJ6RGWPFjMT69OW3 cOZa5LQELDK3w== Date: Wed, 10 Sep 2025 13:19:48 +0100 From: Mark Brown To: dan.j.williams@intel.com Cc: Konstantin Ryabitsev , Linus Torvalds , Jens Axboe , Vlastimil Babka , Jakub Kicinski , "Rafael J. Wysocki" , Caleb Sander Mateos , io-uring , workflows@vger.kernel.org Subject: Re: Link trailers revisited (was Re: [GIT PULL] io_uring fix for 6.17-rc5) Message-ID: References: <92dc8570-84a2-4015-9c7a-6e7da784869a@kernel.dk> <20250909-green-oriole-of-speed-85cd6d@lemur> <497c9c10-3309-49b9-8d4f-ff0bc34df4e5@suse.cz> <20250909-impetuous-swine-of-chaos-2aa9af@meerkat> <68c0d07372c8d_4224d100dc@dwillia2-mobl4.notmuch> Precedence: bulk X-Mailing-List: io-uring@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3RrWNWWD4p39M8rR" Content-Disposition: inline In-Reply-To: <68c0d07372c8d_4224d100dc@dwillia2-mobl4.notmuch> X-Cookie: I think my career is ruined! --3RrWNWWD4p39M8rR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 09, 2025 at 06:12:19PM -0700, dan.j.williams@intel.com wrote: > Konstantin Ryabitsev wrote: > > We can't control how the patches are generated by submitters. If someone > > generates and sends them with --histogram, this won't work. Here's an example > > right from your tree: > Is this a matter of teach git send-email to generate a header, e.g. > "X-Patch-ID:", for a given stable diff format convention? That lets > submitters use any diff format they want, but the X-Patch-ID: is > constant. Then "git show $diff_opts_convention $commit" becomes more > reliable over time. We can't rely on people using git send-email at all, and they might be using an old version (eg, from their distro) even when thy do. > It still does not help the problem of maintainers massaging patches on > their way upstream, but patch.msgid.link does not help that either > because that Link: is not the patch that was merged. So if you care > about automated tooling being able to query lore for commits, the That's not really what people are using these links for - if you have the commit you don't need to go to the mailing list archive to get it. You're more likely to be using them to find the relevant discussion, see who was involved and possibly send some kind of followup (eg, to report a regression in my case). A link tag, especially one with a well defined domain for the links, works fine in this sort of application since it's pointing at the last point the thing was on the list regardless of how poorly what's made it into git corresponds to what was posted. --3RrWNWWD4p39M8rR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmjBbOQACgkQJNaLcl1U h9Bm+gf9Etuh1V61zc0Tmm1qR4YKDzschf9Zc1N2x+BidviOFp64DuGJahcCrXqb CAhcMafY6ak0TK+EzQJtAgo6jKdS72i0lHiZ3KVFT2IofkOsTf3yxRc+qBZ6GjDb A56eICFOkJjYLJqnLlvjhlR+Hl/GFmUEUA6DIJ3UgUYNpqWoGb8bo9my7B7D8ALy BvPXA8CdbeQYZA85UJvg1Y3Dw8yCPragaEN9l5WRxWOgxMb0xhu/NgkJx/s6o0+R aat8vQloZDlNNEy40gLzdf7lLd5Nb0rmcv/5566ubFVdQfTD2xFW0/XlCJdMpSps YBH5va4rvmLCZpxzTlrammurHkHgxg== =rI70 -----END PGP SIGNATURE----- --3RrWNWWD4p39M8rR--