patches for DPDK stable branches
 help / color / mirror / Atom feed
* [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO
@ 2021-02-04 12:09 Christian Ehrhardt
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection Christian Ehrhardt
                   ` (3 more replies)
  0 siblings, 4 replies; 9+ messages in thread
From: Christian Ehrhardt @ 2021-02-04 12:09 UTC (permalink / raw)
  To: dpdk stable; +Cc: Luca Boccassi, Kevin Traynor, Christian Ehrhardt

When we ask for backports the code that we get sent might match latest
dpdk.org:dpdk-stable.git but not our WIP branch.

To mimimize any errors that arise out of that hint at the QUEUED_REPO
int he call for backport-help.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
 3-request-backport | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/3-request-backport b/3-request-backport
index 5749e26..d123531 100755
--- a/3-request-backport
+++ b/3-request-backport
@@ -61,7 +61,20 @@ Can authors check your patches in the following list and either:
 
 Please do either of the above by $(date --date="+7 days" "+%D").
 
+EOF
+
+if [ "$QUEUED_REPO" != "none" ]; then
+	cat << EOF
+You can find the a temporary work-in-progress branch of the coming $stable_release
+release at:
+    ${QUEUED_REPO}
+It is recommended to backport on top of that to minimize further conflicts or
+misunderstandings.
+
+EOF
+fi
 
+cat << EOF
 Some notes on $(stable_or_lts) backports:
 
 A backport should contain a reference to the DPDK main branch commit
-- 
2.30.0


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection
  2021-02-04 12:09 [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Christian Ehrhardt
@ 2021-02-04 12:09 ` Christian Ehrhardt
  2021-02-04 12:26   ` Luca Boccassi
  2021-02-04 13:29   ` Kevin Traynor
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions Christian Ehrhardt
                   ` (2 subsequent siblings)
  3 siblings, 2 replies; 9+ messages in thread
From: Christian Ehrhardt @ 2021-02-04 12:09 UTC (permalink / raw)
  To: dpdk stable; +Cc: Luca Boccassi, Kevin Traynor, Christian Ehrhardt

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@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
 ==================
 
-- 
2.30.0


^ permalink raw reply	[flat|nested] 9+ messages in thread

* [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions
  2021-02-04 12:09 [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Christian Ehrhardt
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection Christian Ehrhardt
@ 2021-02-04 12:09 ` Christian Ehrhardt
  2021-02-04 12:27   ` Luca Boccassi
  2021-02-04 13:30   ` Kevin Traynor
  2021-02-04 12:26 ` [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Luca Boccassi
  2021-02-04 13:30 ` Kevin Traynor
  3 siblings, 2 replies; 9+ messages in thread
From: Christian Ehrhardt @ 2021-02-04 12:09 UTC (permalink / raw)
  To: dpdk stable; +Cc: Luca Boccassi, Kevin Traynor, Christian Ehrhardt

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
 ==================
 
-- 
2.30.0


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO
  2021-02-04 12:09 [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Christian Ehrhardt
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection Christian Ehrhardt
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions Christian Ehrhardt
@ 2021-02-04 12:26 ` Luca Boccassi
  2021-02-04 13:30 ` Kevin Traynor
  3 siblings, 0 replies; 9+ messages in thread
From: Luca Boccassi @ 2021-02-04 12:26 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable; +Cc: Kevin Traynor

On Thu, 2021-02-04 at 13:09 +0100, Christian Ehrhardt wrote:
> When we ask for backports the code that we get sent might match latest
> dpdk.org:dpdk-stable.git but not our WIP branch.
> 
> To mimimize any errors that arise out of that hint at the QUEUED_REPO
> int he call for backport-help.
> 
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
>  3-request-backport | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/3-request-backport b/3-request-backport
> index 5749e26..d123531 100755
> --- a/3-request-backport
> +++ b/3-request-backport
> @@ -61,7 +61,20 @@ Can authors check your patches in the following list and either:
>  
>  Please do either of the above by $(date --date="+7 days" "+%D").
>  
> +EOF
> +
> +if [ "$QUEUED_REPO" != "none" ]; then
> +	cat << EOF
> +You can find the a temporary work-in-progress branch of the coming $stable_release
> +release at:
> +    ${QUEUED_REPO}
> +It is recommended to backport on top of that to minimize further conflicts or
> +misunderstandings.
> +
> +EOF
> +fi
>  
> +cat << EOF
>  Some notes on $(stable_or_lts) backports:
>  
>  A backport should contain a reference to the DPDK main branch commit

Acked-by: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection Christian Ehrhardt
@ 2021-02-04 12:26   ` Luca Boccassi
  2021-02-04 13:29   ` Kevin Traynor
  1 sibling, 0 replies; 9+ messages in thread
From: Luca Boccassi @ 2021-02-04 12:26 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable; +Cc: Kevin Traynor

On Thu, 2021-02-04 at 13:09 +0100, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@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
>  ==================

Acked-by: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions Christian Ehrhardt
@ 2021-02-04 12:27   ` Luca Boccassi
  2021-02-04 13:30   ` Kevin Traynor
  1 sibling, 0 replies; 9+ messages in thread
From: Luca Boccassi @ 2021-02-04 12:27 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable; +Cc: Kevin Traynor

On Thu, 2021-02-04 at 13:09 +0100, 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: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection Christian Ehrhardt
  2021-02-04 12:26   ` Luca Boccassi
@ 2021-02-04 13:29   ` Kevin Traynor
  1 sibling, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2021-02-04 13:29 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable; +Cc: Luca Boccassi

On 04/02/2021 12:09, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@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@redhat.com>



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO
  2021-02-04 12:09 [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Christian Ehrhardt
                   ` (2 preceding siblings ...)
  2021-02-04 12:26 ` [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Luca Boccassi
@ 2021-02-04 13:30 ` Kevin Traynor
  3 siblings, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2021-02-04 13:30 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable; +Cc: Luca Boccassi

On 04/02/2021 12:09, Christian Ehrhardt wrote:
> When we ask for backports the code that we get sent might match latest
> dpdk.org:dpdk-stable.git but not our WIP branch.
> 
> To mimimize any errors that arise out of that hint at the QUEUED_REPO
> int he call for backport-help.
> 
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

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


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions
  2021-02-04 12:09 ` [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions Christian Ehrhardt
  2021-02-04 12:27   ` Luca Boccassi
@ 2021-02-04 13:30   ` Kevin Traynor
  1 sibling, 0 replies; 9+ messages in thread
From: Kevin Traynor @ 2021-02-04 13:30 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable; +Cc: Luca Boccassi

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>


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2021-02-04 13:30 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-04 12:09 [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Christian Ehrhardt
2021-02-04 12:09 ` [dpdk-stable] [PATCH 2/3] README: add hint on git send-email vs flooding protection Christian Ehrhardt
2021-02-04 12:26   ` Luca Boccassi
2021-02-04 13:29   ` Kevin Traynor
2021-02-04 12:09 ` [dpdk-stable] [PATCH 3/3] README: add hint on chaining multiple series submissions Christian Ehrhardt
2021-02-04 12:27   ` Luca Boccassi
2021-02-04 13:30   ` Kevin Traynor
2021-02-04 12:26 ` [dpdk-stable] [PATCH 1/3] 3-request-backport: add hint to QUEUED_REPO Luca Boccassi
2021-02-04 13:30 ` Kevin Traynor

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).