From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, stephen@networkplumber.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] git trees organization
Date: Tue, 12 Sep 2017 17:32:34 +0100 [thread overview]
Message-ID: <613d0513-2a4a-4909-3263-21170b57f099@intel.com> (raw)
In-Reply-To: <2737351.pD9poAUtZC@xps>
Hi Thomas,
On 9/11/2017 11:03 PM, Thomas Monjalon wrote:
> Hi all,
>
> As you know I am currently the only maintainer of the master tree.
> It is very convenient because I need to synchronize with others
> only when pulling "next-*" trees.
> But the drawback is that I should be available very often to
> avoid stalled patches waiting in patchwork backlog.
>
> I feel it is the good time to move to a slightly different organization.
> I am working closely with Ferruh Yigit for almost one year, as next-net
> maintainer, and I think it would be very efficient to delegate him some
> work for the master tree.
> I mean that I would use the patchwork delegation to explicitly divide
> the workload given our different experiences.
> Ferruh, do you agree taking this new responsibility?
ACK, I will do my best.
next prev parent reply other threads:[~2017-09-12 16:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:03 Thomas Monjalon
2017-09-12 8:32 ` Bruce Richardson
2017-09-12 8:48 ` Thomas Monjalon
2017-09-12 13:01 ` Wiles, Keith
2017-09-12 16:34 ` Ferruh Yigit
2017-09-13 7:58 ` Adrien Mazarguil
2017-09-13 11:38 ` Ferruh Yigit
2017-09-13 12:25 ` Adrien Mazarguil
2017-09-13 13:21 ` Ferruh Yigit
2017-09-13 14:54 ` Adrien Mazarguil
2017-09-14 2:25 ` Stephen Hemminger
2017-09-14 8:22 ` Thomas Monjalon
2017-09-14 9:03 ` Bruce Richardson
2017-09-14 9:18 ` Thomas Monjalon
2017-09-14 12:50 ` Wiles, Keith
2017-09-14 9:11 ` Nélio Laranjeiro
2017-09-14 17:57 ` Stephen Hemminger
2017-09-12 16:32 ` Ferruh Yigit [this message]
2017-09-12 20:20 ` 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=613d0513-2a4a-4909-3263-21170b57f099@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).