From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] more maintainers with sub-trees
Date: Tue, 23 Dec 2014 13:58:17 -0500 [thread overview]
Message-ID: <20141223185817.GK31876@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1770408.F1oE5mhdeH@xps13>
On Tue, Dec 23, 2014 at 06:08:26PM +0100, Thomas Monjalon wrote:
> Hello all,
>
> We now have 2 new maintainers managing their own sub-tree for some
> specific areas of DPDK:
> - Stephen Hemminger will maintain the driver bnx2x
> - Helin Zhang will maintain the driver i40e
>
> These repositories can be browsed from the "next" section of this page:
> http://dpdk.org/browse/
>
> Patches should still be sent to dev@dpdk.org for review.
> They will be applied to the sub-tree first, and will be merged in dpdk.git
> after a pull request is submitted.
>
> More sub-trees can be created on demand.
>
Can you describe the expected workflow for these subtrees? I ask because it
seems a bit odd to have a separate subtrees for bnx2x (which doesn't appear to
exist in either tree yet) and i40e, while other pmd's all ostensibly still go
through your tree. I presume that Stephen and Helin will send you merge
requests prior to -rc releases, and that for changes that affect pmd's
tree-wide, we can circumvent the subtree with Stephen/Helin's signoff?
Neil
> --
> Thomas
>
next prev parent reply other threads:[~2014-12-23 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 17:08 Thomas Monjalon
2014-12-23 18:58 ` Neil Horman [this message]
2015-01-16 14:36 ` Thomas Monjalon
2015-01-19 9:54 ` Vlad Zolotarov
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=20141223185817.GK31876@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--cc=thomas.monjalon@6wind.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).