From: George Dunlap <george.dunlap@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
<xen-devel@lists.xenproject.org>
Cc: lars.kurth@citrix.com, julien@xen.org, wl@xen.org,
konrad.wilk@oracle.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, jbeulich@suse.com,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: [Xen-devel] [PATCH] Introduce a description of a new optional tag for Backports
Date: Mon, 11 Nov 2019 14:12:48 +0000 [thread overview]
Message-ID: <a161d23f-391d-3547-4949-ccb95fb09384@citrix.com> (raw)
In-Reply-To: <20191108190952.22163-1-sstabellini@kernel.org>
On 11/8/19 7:09 PM, Stefano Stabellini wrote:
> Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
> CC: jbeulich@suse.com
> CC: george.dunlap@citrix.com
> CC: julien@xen.org
> CC: lars.kurth@citrix.com
> CC: andrew.cooper3@citrix.com
> CC: ian.jackson@eu.citrix.com
> CC: konrad.wilk@oracle.com
> CC: wl@xen.org
> ---
> docs/process/backport-tag.pandoc | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
> create mode 100644 docs/process/backport-tag.pandoc
>
> diff --git a/docs/process/backport-tag.pandoc b/docs/process/backport-tag.pandoc
> new file mode 100644
> index 0000000000..e570efdcc8
> --- /dev/null
> +++ b/docs/process/backport-tag.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.
The text and the idea both look good to me.
But it seems kind of balkanized to put it in its own file. Would it be
better to try to make a slightly more general bit of content? Either
about the backport process, or about tags in general?
(This would simply be renaming the file; not expecting you to generate
extra content.)
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-11 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 19:09 [Xen-devel] [PATCH] Introduce a description of a new optional tag for Backports Stefano Stabellini
2019-11-11 10:50 ` Ian Jackson
2019-11-11 11:35 ` Wei Liu
2019-11-11 14:12 ` George Dunlap [this message]
2019-11-11 14:19 ` Lars Kurth
2019-11-11 17:03 ` Stefano Stabellini
2019-11-11 20:15 ` Lars Kurth
2019-11-12 11:14 ` Anthony PERARD
2019-11-12 11:17 ` Ian Jackson
2019-11-12 17:10 ` Stefano Stabellini
2019-11-12 20:07 ` Lars Kurth
2020-01-29 22:15 ` Julien Grall
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=a161d23f-391d-3547-4949-ccb95fb09384@citrix.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.com \
--cc=wl@xen.org \
--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.