From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, John McNamara <john.mcnamara@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add sub-repositories information
Date: Fri, 11 Nov 2016 18:45:20 +0530 [thread overview]
Message-ID: <d9fa5cc2-1047-73e7-5bd6-08e119f21409@nxp.com> (raw)
In-Reply-To: <20161110172718.2292-1-ferruh.yigit@intel.com>
Hello Ferruh,
Trivial comment/suggestion:
On Thursday 10 November 2016 10:57 PM, Ferruh Yigit wrote:
> DPDK switched to main and sub-repositories approach, this patch
> documents new approach and updates development process according.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> doc/guides/contributing/patches.rst | 18 +++++++++++++++---
> 1 file changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
> index 729aea7..bec9bfc 100644
> --- a/doc/guides/contributing/patches.rst
> +++ b/doc/guides/contributing/patches.rst
> @@ -20,7 +20,14 @@ The DPDK development process has the following features:
> * There is a mailing list where developers submit patches.
> * There are maintainers for hierarchical components.
> * Patches are reviewed publicly on the mailing list.
> -* Successfully reviewed patches are merged to the master branch of the repository.
> +* Successfully reviewed patches are merged to the repository.
> +
> +|
> +
> +* There are main repository ``dpdk`` and sub-repositories ``dpdk-next-*``.
> +* A patch should be sent for its target repository. Like net drivers should be on top of dpdk-next-net repository.
> +* All sub-repositories merged into main repository for -rc1 and -rc2 versions of the release.
'All sub-repositories *are* merged into ...'?
> +* After -rc2 release all patches should target main repository.
>
> The mailing list for DPDK development is `dev@dpdk.org <http://dpdk.org/ml/archives/dev/>`_.
> Contributors will need to `register for the mailing list <http://dpdk.org/ml/listinfo/dev>`_ in order to submit patches.
> @@ -33,12 +40,17 @@ Refer to the `Pro Git Book <http://www.git-scm.com/book/>`_ for further informat
> Getting the Source Code
> -----------------------
>
> -The source code can be cloned using either of the following::
> +The source code can be cloned using either of the following:
>
> - git clone git://dpdk.org/dpdk
> +main repository::
>
> + git clone git://dpdk.org/dpdk
> git clone http://dpdk.org/git/dpdk
>
> +sub-repositories (`list <http://dpdk.org/browse/next>`_)::
> +
> + git clone git://dpdk.org/next/dpdk-next-*
> + git clone http://dpdk.org/git/next/dpdk-next-*
>
> Make your Changes
> -----------------
>
-
Shreyansh
next prev parent reply other threads:[~2016-11-11 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 17:27 Ferruh Yigit
2016-11-11 10:27 ` Mcnamara, John
2016-11-11 13:15 ` Shreyansh Jain [this message]
2016-11-11 13:16 ` Ferruh Yigit
2016-11-11 13:34 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2016-11-14 14:10 ` 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=d9fa5cc2-1047-73e7-5bd6-08e119f21409@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.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).