From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Thomas F Herbert <therbert@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK: Proposal for a patch patch-test integration tree
Date: Thu, 28 May 2015 16:44:37 +0200 [thread overview]
Message-ID: <1533235.gJ5eVabOQh@xps13> (raw)
In-Reply-To: <556728A1.8070403@redhat.com>
2015-05-28 10:39, Thomas F Herbert:
> On 5/28/15 5:48 AM, Thomas Monjalon wrote:
> > 2015-05-27 16:48, Thomas F Herbert:
> >> This is a proposal to create a patch-test dpdk tree. I welcome feedback
> >> from the dpdk community on this proposal.
> >>
> >> This tree will consist of pre-integrated patches submitted to dpdk-dev
> >> mailing list. The purpose of this tree is to help reduce the effort in
> >> reviewing patches and providing feedback to submitters of patches. Also
> >> integrators of dpdk can benefit by having a "linux-next" like tree to
> >> clone and or try new features for performance and breadth of hardware
> >> support. It is the hope that the patch-test tree will provide early
> >> feedback to patch reviewers as well as an assurance of quality to the
> >> project maintainer.
> >
> > Thanks for the proposal. This tree may be hosted here:
> > http://dpdk.org/browse
> > You just have to give the name of the repository and a SSH key.
>
> Shall we call the repo patch-test-next?
Why not dpdk-next?
With this description? Apply and test every patches before acceptance
> I am attaching two public keys to this email
Received, thanks
next prev parent reply other threads:[~2015-05-28 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 20:48 Thomas F Herbert
2015-05-27 21:22 ` Vincent JARDIN
2015-05-28 14:18 ` Thomas F Herbert
[not found] ` <20150527210624.GA15347@mhcomputing.net>
2015-05-27 22:36 ` Thomas F Herbert
2015-05-28 6:54 ` Simon Kågström
2015-05-28 13:10 ` Wiles, Keith
2015-05-28 9:48 ` Thomas Monjalon
[not found] ` <556728A1.8070403@redhat.com>
2015-05-28 14:44 ` Thomas Monjalon [this message]
2015-05-28 15:01 ` Thomas F Herbert
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=1533235.gJ5eVabOQh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=therbert@redhat.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).