From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: add staging tree for network drivers
Date: Mon, 25 Jul 2016 17:21:44 +0100 [thread overview]
Message-ID: <20160725162143.GA34436@bricha3-MOBL3> (raw)
In-Reply-To: <1549168.YBdMqhsz3P@xps13>
On Mon, Jul 25, 2016 at 05:28:40PM +0200, Thomas Monjalon wrote:
> 2016-07-25 16:19, Bruce Richardson:
> > +Staging Trees
> > +-------------
> > +
> > +Networking Drivers
> > +T: git://dpdk.org/dpdk-next-net
> > +M: Bruce Richardson <bruce.richardson@intel.com>
>
> I thought we could write the next- tree information below the
> existing title:
>
> Networking Drivers
> ------------------
>
Maybe, but I think it would work better to have all the staging trees listed
together at the top of the file. Makes it easier to see on opening the file
that they exist.
/Bruce
next prev parent reply other threads:[~2016-07-25 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 15:19 Bruce Richardson
2016-07-25 15:28 ` Thomas Monjalon
2016-07-25 16:21 ` Bruce Richardson [this message]
2016-08-23 0:15 ` De Lara Guarch, Pablo
2016-11-10 12:14 ` Ferruh Yigit
2016-11-10 13:50 ` Thomas Monjalon
2016-11-14 14:04 ` 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=20160725162143.GA34436@bricha3-MOBL3 \
--to=bruce.richardson@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).