[dpdk-dev] [PATCH v2] docs: add default that all fixes should be backported

[Thomas Monjalon]

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 at 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 at dpdk.org