From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] add README
Date: Sun, 13 Dec 2015 21:57:38 +0100 [thread overview]
Message-ID: <58011961.7nmb3QRVgO@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2023CCEC4@IRSMSX103.ger.corp.intel.com>
> > This project is missing a proper README which is used in other projects
> > and some git visualization services.
> > Only a starting point, please feel free to edit.
> > To keep the file short and current, I avoided putting any specific
> > information about features and versions.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-12-13 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 4:20 Stephen Hemminger
2015-12-03 16:18 ` Mcnamara, John
2015-12-13 20:57 ` 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=58011961.7nmb3QRVgO@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).