patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>, stable@dpdk.org, yskoh@mellanox.com
Subject: Re: [dpdk-stable] [PATCH 1/2] compose-notice: update compose-notice text
Date: Fri, 21 Jun 2019 18:16:15 +0100	[thread overview]
Message-ID: <78890a119be642eb8fa0153037d0160ecc697e94.camel@debian.org> (raw)
In-Reply-To: <20190621144015.8749-1-ktraynor@redhat.com>

On Fri, 2019-06-21 at 15:40 +0100, Kevin Traynor wrote:
> I got some feedback that it was confusing, so added a little
> text to explicitly mention that changes would be from rebasing.
> 
> Signed-off-by: Kevin Traynor <
> ktraynor@redhat.com
> >
> ---
>  compose-notice | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/compose-notice b/compose-notice
> index 21cbc68..e44c738 100644
> --- a/compose-notice
> +++ b/compose-notice
> @@ -43,7 +43,9 @@ It will be pushed if I get no objections before
> $(date --date="+2 days" "+%D").
>  shout if anyone has objections.
>  $(cat notice-more 2>/dev/null | grep -v "^#")
> -Also note that after the patch there's a diff of the upstream commit
> vs the patch applied
> -to the branch. If the code is different (ie: not only metadata
> diffs), due for example to
> -a change in context or macro names, please double check it.
> +Also note that after the patch there's a diff of the upstream commit
> vs the
> +patch applied to the branch. This will indicate if there was any
> rebasing
> +needed to apply to the stable branch. If there were code changes for
> rebasing
> +(ie: not only metadata diffs), please double check that the rebase
> was
> +correctly done.
>  
>  EOF

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

-- 
Kind regards,
Luca Boccassi

      parent reply	other threads:[~2019-06-21 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 14:40 Kevin Traynor
2019-06-21 14:40 ` [dpdk-stable] [PATCH 2/2] 5-make-release-commit: Update release notes Kevin Traynor
2019-06-21 17:16   ` Luca Boccassi
2019-06-21 17:16 ` Luca Boccassi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=78890a119be642eb8fa0153037d0160ecc697e94.camel@debian.org \
    --to=bluca@debian.org \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=yskoh@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).