Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id ECC8CC74A5B for ; Tue, 14 Mar 2023 14:13:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229865AbjCNON0 (ORCPT ); Tue, 14 Mar 2023 10:13:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60790 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229790AbjCNONW (ORCPT ); Tue, 14 Mar 2023 10:13:22 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 64C26A42EC; Tue, 14 Mar 2023 07:12:55 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 4761F21F48; Tue, 14 Mar 2023 14:12:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1678803148; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Q0HjvnKbml+YdcLLE7DMO0MaJnPS3khjsSC2B2uEuwo=; b=QXdStDC3u29eG6VvG5yUEI1E+896xhnAECIuv+0PhGzoJ3EYSxQ/z6ymoeF6nPvcUjX55k 9rqLh/hsV5w3Fql1CVkywHbc5UVjuHA0dDKaPJAtU+gyrKtbBQsg8/omdBY1Mef2bJ1cEB t3VtiyemZp1lDHZ4T5S4Lnz8QA81h9M= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1678803148; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Q0HjvnKbml+YdcLLE7DMO0MaJnPS3khjsSC2B2uEuwo=; b=BHqiCNJyvFqs1LJLRJENn60nI3LRSVNTA6AmP6Xo3wGJxpkXbVD8rnK/0CvWLdLaF85B7j qW1wAzcx1JKiwVDQ== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 3B3E413A26; Tue, 14 Mar 2023 14:12:28 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id /zFqDsyAEGTUFAAAMHmgww (envelope-from ); Tue, 14 Mar 2023 14:12:28 +0000 Received: by quack3.suse.cz (Postfix, from userid 1000) id C1602A06FD; Tue, 14 Mar 2023 15:12:27 +0100 (CET) Date: Tue, 14 Mar 2023 15:12:27 +0100 From: Jan Kara To: Theodore Ts'o Cc: Willy Tarreau , David Laight , 'Sasha Levin' , Matthew Wilcox , Eric Biggers , Pavel Machek , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , "viro@zeniv.linux.org.uk" , "linux-fsdevel@vger.kernel.org" Subject: Re: AUTOSEL process Message-ID: <20230314141227.7x6k2wsveliooclw@quack3> References: <9ff6fe2c13434512b034823112843d4f@AcuMS.aculab.com> <20230312050947.GK860405@mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230312050947.GK860405@mit.edu> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun 12-03-23 00:09:47, Theodore Ts'o wrote: > On Sun, Mar 12, 2023 at 05:41:07AM +0100, Willy Tarreau wrote: > > > > I suspect that having an option to keep the message ID in the footer (a > > bit like the "cherry-picked from" tag but instead "blongs to series") > > could possibly help. And when no such info is present we could have > > one ID generated per "git am" execution since usually if you apply an > > mbox, it constitutes a series (but not always of course, though it's > > not difficult to arrange series like this). > > As I pointed out earlier, some of us are adding the message ID in the > footer alrady, using a Link tag. This is even documented already in > the Kernel Maintainer's Handbook, so I'm pretty sure it's not just me. :-) Yeah, given Linus' rants about links pointing to patch posting, what I'm currently doing is that I add Message-ID: tag to the patch instead of a Link: tag. It preserves the information as well and it is obvious to human reader what are links to reports / discussions and what is just a link to patch posting. Honza -- Jan Kara SUSE Labs, CR