From: Harini Ramakrishnan <Harini.Ramakrishnan@microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ranjit Menon <ranjit.menon@intel.com>,
"cathal.ohare@intel.com" <cathal.ohare@intel.com>,
"pallavi.kadam@intel.com" <pallavi.kadam@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"rasland@mellanox.com" <rasland@mellanox.com>,
Adham Masarwah <adham@mellanox.com>,
Eilon Greenstein <eilong@mellanox.com>,
Anan Saif <anans@mellanox.com>,
Rani Sharoni <ranish@mellanox.com>, Tal Alon <talal@mellanox.com>,
Yohad Tor <yohadt@mellanox.com>,
Omar Cardona <ocardona@microsoft.com>,
"Haseeb.Gani@cavium.com" <Haseeb.Gani@cavium.com>,
"shshaikh@marvell.com" <shshaikh@marvell.com>,
"nareshkumar.pbs@broadcom.com" <nareshkumar.pbs@broadcom.com>
Subject: Re: [dpdk-dev] DPDK Windows Community call - 02 May 2019
Date: Tue, 14 May 2019 16:52:37 +0000 [thread overview]
Message-ID: <MWHPR21MB0638146424D54E3EB0CA3DD4EF080@MWHPR21MB0638.namprd21.prod.outlook.com> (raw)
In-Reply-To: <2605026.pMiyh1GXVC@xps>
> - Draft repo needs a new branch to host latest Windows development
> - currently WIP
> Please, which up-to-date branch we can work on?
"windpdk-next-dev" branch in the Windows DPDK draft repository is the most up to date branch that is currently a mirror of the upstream DPDK repository.
http://git.dpdk.org/draft/dpdk-draft-windows/log/?h=windpdk-next-dev
Also, "windpdk-v18.08-clang" branch has been created. This is Windows port of v18.08 with clang support.
next prev parent reply other threads:[~2019-05-14 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 23:34 Ranjit Menon
2019-05-09 23:34 ` Ranjit Menon
2019-05-14 15:48 ` Thomas Monjalon
2019-05-14 15:48 ` Thomas Monjalon
2019-05-14 16:52 ` Harini Ramakrishnan [this message]
2019-05-14 16:52 ` Harini Ramakrishnan
2019-05-16 9:41 ` Thomas Monjalon
2019-05-16 9:41 ` Thomas Monjalon
2019-05-16 13:10 ` 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=MWHPR21MB0638146424D54E3EB0CA3DD4EF080@MWHPR21MB0638.namprd21.prod.outlook.com \
--to=harini.ramakrishnan@microsoft.com \
--cc=Haseeb.Gani@cavium.com \
--cc=adham@mellanox.com \
--cc=anans@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=cathal.ohare@intel.com \
--cc=dev@dpdk.org \
--cc=eilong@mellanox.com \
--cc=nareshkumar.pbs@broadcom.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranish@mellanox.com \
--cc=ranjit.menon@intel.com \
--cc=rasland@mellanox.com \
--cc=shshaikh@marvell.com \
--cc=talal@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yohadt@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).