patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: yskoh@mellanox.com
Cc: Luca Boccassi <bluca@debian.org>,
	stable@dpdk.org, Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [dpdk-stable] [PATCH stable-scripts] Add diff-of-diff below backported patch to 2-notice
Date: Wed, 22 Aug 2018 14:33:07 +0200	[thread overview]
Message-ID: <CAATJJ0JSj_VDJKd0GYZ_BE4488x1R-n1UZdgxb9G4-WewWaHcA@mail.gmail.com> (raw)
In-Reply-To: <5E9BE43A-561C-4AA1-BF62-1DEF22C2F9FB@mellanox.com>

On Mon, Aug 20, 2018 at 8:28 PM Yongseok Koh <yskoh@mellanox.com> wrote:

>
> > On Aug 20, 2018, at 11:03 AM, bluca@debian.org wrote:
> >
> > From: Luca Boccassi <bluca@debian.org>
> >
> > We noticed that it's not clear if a patch is cleanly cherry-picked or if
> > it gets adjusted due to merge conflicts.
> > This change will add to the backport notice email a diff-of-diffs, and
> > a note asking the developer/maintainer to review it.
> > This way it the work we do will be more transparent.
> >
> > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > ---
>
> Terrific!
>
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
>

After our discussion that turns out less code than I was expecting.
Even better !
And certainly very useful - thanks!

Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

Thanks
>


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

      reply	other threads:[~2018-08-22 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 18:03 bluca
2018-08-20 18:28 ` Yongseok Koh
2018-08-22 12:33   ` Christian Ehrhardt [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=CAATJJ0JSj_VDJKd0GYZ_BE4488x1R-n1UZdgxb9G4-WewWaHcA@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=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).