From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 882EAA0524 for ; Thu, 4 Feb 2021 14:29:35 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 68F092406C8; Thu, 4 Feb 2021 14:29:35 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id F3CA22406C8 for ; Thu, 4 Feb 2021 14:29:34 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612445373; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iYQPth2c+6zY0MtZ1hMmXuTPw6PpYKTVOxHzLXbWIhE=; b=eFnqNts9wJU+rhhZ5dB1UYjQqAqVCnUCIQgakDL7B6D1ZGw/HExcrZSbMMZ879HE/mtswv l1DkAGttj5PE7+lt+GiM6+k0GnCh+px9Wg+JgSQfFFhYDxUuiVMK/m243XG9Nv2kbMFvnH BqY+SQh+eAQOn0KvKbglBkWHfvxvRIc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-347-wF51b19-MnuCDE524tMpvA-1; Thu, 04 Feb 2021 08:29:31 -0500 X-MC-Unique: wF51b19-MnuCDE524tMpvA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 03D3F107ACC7; Thu, 4 Feb 2021 13:29:30 +0000 (UTC) Received: from [10.36.112.238] (ovpn-112-238.ams2.redhat.com [10.36.112.238]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0AAE15D6D7; Thu, 4 Feb 2021 13:29:28 +0000 (UTC) To: Christian Ehrhardt , dpdk stable Cc: Luca Boccassi References: <20210204120903.2515011-1-christian.ehrhardt@canonical.com> <20210204120903.2515011-2-christian.ehrhardt@canonical.com> From: Kevin Traynor Message-ID: Date: Thu, 4 Feb 2021 13:29:27 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: <20210204120903.2515011-2-christian.ehrhardt@canonical.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ktraynor@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On 04/02/2021 12:09, Christian Ehrhardt wrote: > Signed-off-by: Christian Ehrhardt > --- > 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