[dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection
Kevin Traynor
ktraynor at redhat.com
Thu Feb 4 14:29:27 CET 2021
On 04/02/2021 12:09, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt at canonical.com>
> ---
> README | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/README b/README
> index 3e4978a..771b97e 100644
> --- a/README
> +++ b/README
> @@ -87,6 +87,17 @@ 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:
> +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
> +>100 mails at once. To avoid being blocked in between a submission by flood
> +protection that is active for some common providers smtp services consider
> +adding the following to your gitconfig:
> + [sendemail]
> + smtpBatchSize = 5
> + smtpReloginDelay = 10
> +
> 3-request-backport
> ==================
>
>
Ah, so *that* is why they never replied... :-)
Acked-by: Kevin Traynor <ktraynor at redhat.com>
More information about the stable
mailing list