From nobody Wed May 8 22:58:33 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of lists.xenproject.org designates 192.237.175.120 as permitted sender) client-ip=192.237.175.120; envelope-from=xen-devel-bounces@lists.xenproject.org; helo=lists.xenproject.org; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of lists.xenproject.org designates 192.237.175.120 as permitted sender) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org; dmarc=fail(p=none dis=none) header.from=kernel.org ARC-Seal: i=1; a=rsa-sha256; t=1587162296; cv=none; d=zohomail.com; s=zohoarc; b=Rto0dMD2vEKEZyqw+aCPMyXYgAoEb6lINF6yfnhSr/nWM2wDhJCRFIixHNDm/deJRbbH7VWaSSDvcnNp0bsZS/g7qCe84ek1c1tViywPOzFSXpAMBcvQuguxQ7uWwj9x33/YKE6PgtKtT8rcxhy3yM8M/srWC3y+iAAYHIMEUUk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1587162296; h=Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Help:List-Unsubscribe:Message-ID:Sender:Subject:To; bh=5Ka4aM7oi8ao3ikwaEBI0zlDiVNmGdBM8K0nrrZNIC0=; b=bU8sDmskEb9iN8R8VZbUrFq/JXedQnyA4ZaQ3Gcb/Vc1N2v3Ku2n9miZp00GAe8uhbxvvfA1OURZrUx1DqrGGMr6A4MHtmzndnwPgq9UAcGoXfVb/wXw/gQNQDullsgWEkJQkixMddAZthaNh9K2lkEkBmrU6kw41Aj4dimGX7o= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of lists.xenproject.org designates 192.237.175.120 as permitted sender) smtp.mailfrom=xen-devel-bounces@lists.xenproject.org; dmarc=fail header.from= (p=none dis=none) header.from= Return-Path: Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) by mx.zohomail.com with SMTPS id 1587162296509870.8013548675051; Fri, 17 Apr 2020 15:24:56 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1jPZPX-0007WZ-Jw; Fri, 17 Apr 2020 22:24:35 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1jPZPW-0007WU-Is for xen-devel@lists.xenproject.org; Fri, 17 Apr 2020 22:24:34 +0000 Received: from mail.kernel.org (unknown [198.145.29.99]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 3607e930-80fa-11ea-8da7-12813bfff9fa; Fri, 17 Apr 2020 22:24:32 +0000 (UTC) Received: from sstabellini-ThinkPad-T480s.hsd1.ca.comcast.net (c-67-164-102-47.hsd1.ca.comcast.net [67.164.102.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id ADE7620776; Fri, 17 Apr 2020 22:24:31 +0000 (UTC) X-Inumbo-ID: 3607e930-80fa-11ea-8da7-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587162272; bh=cN63QuJZ8sbvvVXA8yUyWE0xtwrSWuim3k/SqZ0/+6s=; h=From:To:Cc:Subject:Date:From; b=1nsPArcMvOrzXecHYcu/RaV5/lggz+hPIY5Lox0FWfn3kyDwzeiXIesyIADqYyaKQ 9nl1oDEONHt6jCqyjB+p9JSoZhqn0n5luoIYD7TIprldDWL4sp8uwQOv3r5sMQapaY m9CA0pb0RhC42igYiWTBIVGCGpqty/ygXFPLVZD4= From: Stefano Stabellini To: xen-devel@lists.xenproject.org Subject: [PATCH v3] Introduce a description of the Backport and Fixes tags Date: Fri, 17 Apr 2020 15:24:30 -0700 Message-Id: <20200417222430.20480-1-sstabellini@kernel.org> X-Mailer: git-send-email 2.17.1 X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Cc: lars.kurth@citrix.com, sstabellini@kernel.org, julien@xen.org, Wei Liu , konrad.wilk@oracle.com, andrew.cooper3@citrix.com, Ian Jackson , george.dunlap@citrix.com, jbeulich@suse.com, Stefano Stabellini Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" X-ZohoMail-DKIM: fail (Header signature does not verify) Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Create a new document under docs/process to describe our special tags. Add a description of the Fixes tag and the new Backport tag. Also clarify that lines with tags should not be split. Signed-off-by: Stefano Stabellini CC: Ian Jackson CC: Wei Liu CC: jbeulich@suse.com CC: george.dunlap@citrix.com CC: julien@xen.org CC: lars.kurth@citrix.com CC: andrew.cooper3@citrix.com CC: konrad.wilk@oracle.com Acked-by: Wei Liu --- Removing Acks as I added the description of "Fixes" --- docs/process/tags.pandoc | 55 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 docs/process/tags.pandoc diff --git a/docs/process/tags.pandoc b/docs/process/tags.pandoc new file mode 100644 index 0000000000..06b06dda01 --- /dev/null +++ b/docs/process/tags.pandoc @@ -0,0 +1,55 @@ +Tags: No line splitting +----------------------- +Do not split a tag across multiple lines, tags are exempt from the +"wrap at 75 columns" rule in order to simplify parsing scripts. For +example: + + Fixes: 67d01cdb5 ("x86: infrastructure to allow converting certain= indirect calls to direct ones") + + +Fixes Tag +--------- + +If your patch fixes a bug in a specific commit, e.g. you found an issue us= ing +``git bisect``, please use the 'Fixes:' tag with the first 12 characters of +the SHA-1 ID, and the one line summary. + +The following ``git config`` settings can be used to add a pretty format f= or +outputting the above style in the ``git log`` or ``git show`` commands: + + [core] + abbrev =3D 12 + [pretty] + fixes =3D Fixes: %h (\"%s\") + + +Backport Tag +------------ + +A backport tag is an optional tag in the commit message to request a +given commit to be backported to the stable trees: + + Backport: 4.9+ + +It marks a commit for being a candidate for backports to all stable +trees from 4.9 onward. + +The backport requester is expected to specify which currently supported +releases need the backport; but encouraged to specify a release as far +back as possible which applies. If the requester doesn't know the oldest +affected tree, they are encouraged to append a comment like the +following: + + Backport: 4.9+ # maybe older + +Maintainers request the Backport tag to be added on commit. Contributors +are welcome to mark their patches with the Backport tag when they deem +appropriate. Maintainers will request for it to be removed when that is +not the case. + +Please note that the Backport tag is a **request** for backport, which +will still need to be evaluated by the stable tree maintainers. +Maintainers might ask the requester to help with the backporting work if +it is not trivial. + +When possible, please use the Fixes tag instead. --=20 2.17.1