On 11/8/19 7:09 PM, Stefano Stabellini wrote: > Signed-off-by: Stefano Stabellini <[email protected]> > CC: [email protected] > CC: [email protected] > CC: [email protected] > CC: [email protected] > CC: [email protected] > CC: [email protected] > CC: [email protected] > CC: [email protected] > --- > 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 [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
