From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"techboard@dpdk.org" <techboard@dpdk.org>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [PATCH 1/2] license/README: fix pathnames and add MIT
Date: Mon, 17 Oct 2022 20:10:21 -0700 [thread overview]
Message-ID: <20221017201021.6f8fafdc@hermes.local> (raw)
In-Reply-To: <AS8PR04MB9064FC3A9F880F2B46D043CD89289@AS8PR04MB9064.eurprd04.prod.outlook.com>
On Tue, 18 Oct 2022 02:46:40 +0000
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> > -----Original Message-----
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: Tuesday, October 18, 2022 7:35 AM
> > To: dev@dpdk.org
> > Cc: techboard@dpdk.org; Stephen Hemminger
> > <stephen@networkplumber.org>; Ferruh Yigit <ferruh.yigit@amd.com>
> > Subject: [PATCH 1/2] license/README: fix pathnames and add MIT
> >
> > The pathnames in the license directory README are incorrect.
> > The current repository puts license text in license/ not licenses/.
>
> [Hemant] Can you break it into two parts:
> 1. for correcting the pathname - this can be merged asap.
> 2. adding MIT license - this need to wait till GB approval.
It is two patches already.
The first one is fixing up existing text.
The second is adding MIT license which needs TB/GB approval
>
next prev parent reply other threads:[~2022-10-18 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 16:32 [PATCH] " Stephen Hemminger
2022-10-05 21:32 ` Ferruh Yigit
2022-10-18 2:04 ` [PATCH 1/2] " Stephen Hemminger
2022-10-18 2:04 ` [RFC 2/2] license: add using MIT license in base code Stephen Hemminger
2022-10-18 2:46 ` [PATCH 1/2] license/README: fix pathnames and add MIT Hemant Agrawal
2022-10-18 3:10 ` Stephen Hemminger [this message]
2022-10-18 7:38 ` Thomas Monjalon
2022-10-19 18:42 ` [PATCH 1/2] license/README: fix pathnames Stephen Hemminger
2022-10-19 18:42 ` [PATCH 2/2] license: add MIT license exception for gve driver Stephen Hemminger
2022-10-27 10:28 ` Thomas Monjalon
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=20221017201021.6f8fafdc@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=hemant.agrawal@nxp.com \
--cc=techboard@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).