From: Remy Horton <remy.horton@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] decision process to accept new libraries
Date: Fri, 24 Feb 2017 11:33:11 +0000 [thread overview]
Message-ID: <4322b761-83d7-2e23-5fdc-c5b493a95ca2@intel.com> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126527526E0@IRSMSX108.ger.corp.intel.com>
On 22/02/2017 19:06, Dumitrescu, Cristian wrote:
[..]
> This essentially leads to the "other" repos becoming second class
> citizens that can be broken at any time without prior notice or the
> right to influence the change. The amount of maintenance work becomes
> very difficult to quantify (e.g. we all know what a ripple effect a
> chance in the mbuf structure can cause to any of those "other" DPDK
> libraries).
+1 - In my experience anything other than a single repository ends up in
tears sooner or later. At a previous company I worked on a project where
each "module" went into its own repo, all fourty-five of which were
strung together using Gerrit/Jenkins, the result being I spent more time
on rebases and build breakages than writing business logic. Patchsets
that cross repo boundaries are a recipe for pain, and if DPDK goes down
the same route, it will likley cripple development.
next prev parent reply other threads:[~2017-02-24 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 10:22 [dpdk-dev] DPDK Technical Board Meeting, 2017-02-15 Richardson, Bruce
2017-02-17 11:16 ` [dpdk-dev] decision process to accept new libraries Thomas Monjalon
2017-02-21 13:46 ` Bruce Richardson
2017-02-21 14:42 ` Thomas Monjalon
2017-02-22 18:39 ` Dumitrescu, Cristian
2017-02-22 19:06 ` Dumitrescu, Cristian
2017-02-24 11:33 ` Remy Horton [this message]
2017-02-24 13:10 ` Thomas Monjalon
2017-02-24 13:17 ` Olivier Matz
2017-02-24 13:25 ` Bruce Richardson
2017-02-24 14:26 ` Olivier Matz
2017-02-24 13:07 ` Thomas Monjalon
2017-02-24 13:17 ` Bruce Richardson
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=4322b761-83d7-2e23-5fdc-c5b493a95ca2@intel.com \
--to=remy.horton@intel.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--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).