From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org,
"colin.king@canonical.com" <colin.king@canonical.com>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-dev] [PATCH] doc: change tools guide to SPDX license
Date: Mon, 05 Aug 2019 16:17:41 +0200 [thread overview]
Message-ID: <11110439.hr5KLOPsxe@xps> (raw)
In-Reply-To: <VI1PR0401MB2541E6C3BCBACD696A6A76D089DE0@VI1PR0401MB2541.eurprd04.prod.outlook.com>
01/08/2019 09:15, Hemant Agrawal:
> Hi Thomas,
> Please apply this patch.
> Regards,
> Hemant
> On Wed, Jun 6, 2018 at 5:39 PM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> >
> > Christian,
> > Will you please ack it? A ack from canonical is must to change the license (even if it is just the style).
>
> Sorry Hemant for the extra delay, I was on PTO and this was lost in the mail flood afterwards.
> Thanks Thomas & Colin for the extra pings to not get lost.
>
> Acked-By: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Applied, thanks
prev parent reply other threads:[~2019-08-05 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 7:50 [PATCH] doc: change tools guide to SPDX license Hemant Agrawal
2018-06-05 7:50 ` [PATCH] doc: add SPDX and copyright to rel notes Hemant Agrawal
2018-07-26 20:44 ` Thomas Monjalon
2018-07-27 4:54 ` [PATCH v2] " Hemant Agrawal
2018-08-09 20:36 ` Thomas Monjalon
2018-06-05 7:50 ` [PATCH] doc: add SPDX and copyright to contributing guide Hemant Agrawal
2018-08-09 20:45 ` Thomas Monjalon
2018-06-05 7:50 ` [PATCH] buildtools: change license to SPDX Hemant Agrawal
2018-06-05 11:27 ` Neil Horman
2018-07-26 20:45 ` Thomas Monjalon
2018-07-04 7:21 ` [PATCH] doc: change tools guide to SPDX license Hemant Agrawal
2018-09-26 15:47 ` Hemant Agrawal
2019-08-01 7:15 ` [dpdk-dev] " Hemant Agrawal
2019-08-05 14:17 ` Thomas Monjalon [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=11110439.hr5KLOPsxe@xps \
--to=thomas@monjalon.net \
--cc=christian.ehrhardt@canonical.com \
--cc=colin.king@canonical.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.