From: Anthony PERARD <anthony.perard@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.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, george.dunlap@citrix.com,
jbeulich@suse.com, xen-devel@lists.xenproject.org,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: [Xen-devel] [PATCH] Introduce a description of a new optional tag for Backports
Date: Tue, 12 Nov 2019 11:14:16 +0000 [thread overview]
Message-ID: <20191112111416.GA2337@perard.uk.xensource.com> (raw)
In-Reply-To: <20191108190952.22163-1-sstabellini@kernel.org>
On Fri, Nov 08, 2019 at 11:09:52AM -0800, Stefano Stabellini wrote:
> +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
[...]
Should we describe the Fixes: tag as well? These would have a similar
purpose to the backport tag, I mean it could help figure out which
commit to backport to which tree.
--
Anthony PERARD
_______________________________________________
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-12 11:14 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
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 [this message]
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=20191112111416.GA2337@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@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.