Re: [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions

[Kevin Traynor <ktraynor@redhat.com>]

On 04/02/2021 12:09, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
>  README | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/README b/README
> index 771b97e..6489379 100644
> --- a/README
> +++ b/README
> @@ -87,7 +87,7 @@ changes. To aid this, a personal repo like github can be used to store the queue
>  patches and it can be referenced in the email. If it is available it is set it
>  in lib.sh with QUEUED_REPO.
>  
> -Note:
> +Note - flood protection:
>  Once generally configured git send-email can submit those via:
>    $ git send-email $release/$date/mail/*.patch
>  But some email providers will apply limits and a DPDK LTS maintainers often send
> @@ -98,6 +98,13 @@ adding the following to your gitconfig:
>          smtpBatchSize = 5
>          smtpReloginDelay = 10
>  
> +Note - chain patch series submissions:
> +Often one is working on the commits collected from lastrelease->rc1, to later
> +work  again on e.g. rc1->rc2. To thread/chain these submissions right
> +git send-email will ask for:
> +    Message-ID to be used as In-Reply-To for the first email (if any)?
> +Here enter the Message-ID of the last patch of your formerly submitted series.
> +
>  3-request-backport
>  ==================
>  
> 

Acked-by: Kevin Traynor <ktraynor@redhat.com>