From: Yongseok Koh <yskoh@mellanox.com>
To: "bluca@debian.org" <bluca@debian.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>
Subject: Re: [dpdk-stable] [PATCH stable-scripts] Add diff-of-diff below backported patch to 2-notice
Date: Mon, 20 Aug 2018 18:28:21 +0000 [thread overview]
Message-ID: <5E9BE43A-561C-4AA1-BF62-1DEF22C2F9FB@mellanox.com> (raw)
In-Reply-To: <20180820180357.26095-1-bluca@debian.org>
> 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>
Thanks
next prev parent reply other threads:[~2018-08-20 18:28 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 [this message]
2018-08-22 12:33 ` Christian Ehrhardt
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=5E9BE43A-561C-4AA1-BF62-1DEF22C2F9FB@mellanox.com \
--to=yskoh@mellanox.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
/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).