From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [96.44.175.130]) (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 88CFD6D13; Wed, 14 Apr 2021 14:03:21 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 86EE81280756; Wed, 14 Apr 2021 06:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hansenpartnership.com; s=20151216; t=1618408634; bh=fFYzX/6FW24mbCHM7bPY08gpKpNGpMuCzn80gOQjgP8=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References:From; b=AypGDemxgaeAQdBjCuxCy3cU8RxpMZmBNwSHkSWYRDGNV/QolXLwJyABcz5lP+Ah5 sdaIj7dTQmLn4X1pZQtr79mDC/cJ2M2JIKIKC7aKnC1RfEyWwGG1Ofd6QRMKZei5KK bEooqrO8F+uxZ1JoM6Hy22iKX++HCykrNlZY+98Q= Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9tpr1tX3UJMt; Wed, 14 Apr 2021 06:57:14 -0700 (PDT) Received: from jarvis.int.hansenpartnership.com (unknown [IPv6:2601:600:8280:66d1::527]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 139FE12806D3; Wed, 14 Apr 2021 06:57:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hansenpartnership.com; s=20151216; t=1618408634; bh=fFYzX/6FW24mbCHM7bPY08gpKpNGpMuCzn80gOQjgP8=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References:From; b=AypGDemxgaeAQdBjCuxCy3cU8RxpMZmBNwSHkSWYRDGNV/QolXLwJyABcz5lP+Ah5 sdaIj7dTQmLn4X1pZQtr79mDC/cJ2M2JIKIKC7aKnC1RfEyWwGG1Ofd6QRMKZei5KK bEooqrO8F+uxZ1JoM6Hy22iKX++HCykrNlZY+98Q= Message-ID: <2f6c16aea7593e25d51ed54501d462443d4b9012.camel@HansenPartnership.com> Subject: Re: RFC: Superseded-by: follow-up trailer From: James Bottomley To: Jason Gunthorpe , Peter Zijlstra Cc: Steven Rostedt , "Jason A. Donenfeld" , Alex Elder , users@linux.kernel.org, tools@linux.kernel.org Date: Wed, 14 Apr 2021 06:57:13 -0700 In-Reply-To: <20210414114950.GM227011@ziepe.ca> References: <20210413204932.yovoa7njwc56jo5v@nitro.local> <20210413172901.1465307c@gandalf.local.home> <20210413214031.fenjvgh5helyuqdz@nitro.local> <20210414114950.GM227011@ziepe.ca> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 X-Mailing-List: tools@linux.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit On Wed, 2021-04-14 at 08:49 -0300, Jason Gunthorpe wrote: > b4 does a nice job helping the maintainer, but the submitter has no > helpful common tooling currently. We have git-format-patch/git-send-email. I like the --cover-from- description of git-format-email but I really think we should use more fields and make it automatic. It would certainly be helpful if it tracked the last version sent of the same branch so I didn't have to add --version. It can't, unfortunately, track message id's because that's generated by git-send-email (has to be that way because resends need different message id's). but suppose git-send-email used fields to track the cover letter message id and version (provided it's called from the git tree), git-format-patch could use them to add a link to the prior version. The problem with the above is it's very fragile when done by two tools the latter of which might not be executed from the tree. It really sounds like we need a combined tool for this, which includes the ability to resend patch series as well as to increment the version. James