From: Stefano Stabellini <sstabellini@kernel.org>
To: xen-devel@lists.xenproject.org
Cc: lars.kurth@citrix.com, sstabellini@kernel.org, julien@xen.org,
konrad.wilk@oracle.com, andrew.cooper3@citrix.com,
george.dunlap@citrix.com, jbeulich@suse.com,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: [PATCH v2] Introduce a description of a new optional tag for Backports
Date: Fri, 10 Apr 2020 09:49:42 -0700 [thread overview]
Message-ID: <20200410164942.9747-1-sstabellini@kernel.org> (raw)
Create a new document under docs/process to describe our special tags.
For now, only add the new backport tag.
Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Acked-by: Wei Liu <wl@xen.org>
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
---
This is the original thread: https://marc.info/?l=xen-devel&m=157324027614941
The backport tag was agreed upon. George requested the file to be
renamed to something more generic, where we could add more information
later.
I kept the original content and acked-by. I renamed the file to
tags.pandoc.
---
docs/process/tags.pandoc | 23 +++++++++++++++++++++++
1 file changed, 23 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..e570efdcc8
--- /dev/null
+++ b/docs/process/tags.pandoc
@@ -0,0 +1,23 @@
+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: all
+
+It marks a commit for being a candidate for backports to all relevant
+trees.
+
+ Backport: 4.9+
+
+It marks a commit for being a candidate for backports to all stable
+trees from 4.9 onward.
+
+Maintainers request the Backport tag to be added on commit.
+Contributors are also 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.
--
2.17.1
next reply other threads:[~2020-04-10 16:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 16:49 Stefano Stabellini [this message]
2020-04-10 17:51 ` [PATCH v2] Introduce a description of a new optional tag for Backports Julien Grall
2020-04-14 7:52 ` Jan Beulich
2020-04-14 16:54 ` Stefano Stabellini
2020-04-15 6:23 ` Jan Beulich
2020-04-15 9:43 ` George Dunlap
2020-04-15 9:49 ` Julien Grall
2020-04-15 9:56 ` George Dunlap
2020-04-15 10:44 ` Jan Beulich
2020-04-16 21:14 ` Stefano Stabellini
2020-04-17 6:51 ` Jan Beulich
2020-04-15 10:36 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200410164942.9747-1-sstabellini@kernel.org \
--to=sstabellini@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=stefano.stabellini@xilinx.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.