From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: john.mcnamara@intel.com, bluca@debian.org, yskoh@mellanox.com,
christian.ehrhardt@canonical.com, dev@dpdk.org,
aconole@redhat.com, ferruh.yigit@intel.com
Subject: Re: [PATCH v2] docs: add default that all fixes should be backported
Date: Sat, 30 Jun 2018 00:02:14 +0200 [thread overview]
Message-ID: <9109842.NZQjWO3Re5@xps> (raw)
In-Reply-To: <1530308851-30496-1-git-send-email-ktraynor@redhat.com>
29/06/2018 23:47, Kevin Traynor:
> -Backporting should be limited to bug fixes.
> +Backporting should be limited to bug fixes. All patches accepted on the master
> +branch with Fixes tags should be backported to the relevant stable/LTS branches,
> +unless the submitter indicates otherwise. If there are exceptions, they will be
> +discussed on the mailing lists.
>
> Features should not be backported to stable releases. It may be acceptable, in
> @@ -77,5 +80,6 @@ list.
> All fix patches to the master branch that are candidates for backporting
> should also be CCed to the `stable@dpdk.org <http://dpdk.org/ml/listinfo/stable>`_
> -mailing list.
> +mailing list. Absence of this CC is an indication that the patch is not suitable
> +for backporting.
We should mention that it is not a matter of Cc'ing the dpdk-stable ML,
but more importantly, a tag which remains in the git history:
Cc: stable@dpdk.org
next prev parent reply other threads:[~2018-06-29 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:00 [PATCH] docs: add default that all fixes are backported Kevin Traynor
2018-06-21 16:14 ` Luca Boccassi
2018-06-21 16:45 ` Ferruh Yigit
2018-06-29 16:15 ` Thomas Monjalon
2018-06-29 21:39 ` Kevin Traynor
2018-06-29 21:56 ` Thomas Monjalon
2018-06-21 18:00 ` Aaron Conole
2018-06-29 21:47 ` [PATCH v2] docs: add default that all fixes should be backported Kevin Traynor
2018-06-29 22:02 ` Thomas Monjalon [this message]
2018-06-29 23:15 ` Kevin Traynor
2018-06-29 23:10 ` [PATCH v3] " Kevin Traynor
2018-07-04 15:22 ` Thomas Monjalon
2018-07-11 21:04 ` Thomas Monjalon
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=9109842.NZQjWO3Re5@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=yskoh@mellanox.com \
/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.