From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH 1/3] move up contribution guidelines link
Date: Wed, 27 Jul 2016 15:24:12 +0200 [thread overview]
Message-ID: <20160727132412.GT14792@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <3223598.qfeAjWIXaX@xps13>
On Wed, Jul 27, 2016 at 03:01:09PM +0200, Thomas Monjalon wrote:
> 2016-07-27 14:15, Nelio Laranjeiro:
> > Too many people consider this section as a main reference whereas it is
> > only a snippet of the fully detailed contribution guides. Moving it to the
> > beginning of the section should help newbies to read it instead of applying
> > a bash of command lines which rarely ends well.
>
> Not so rarely :)
For myself, it was :)
I will change it in v2 for less.
>
> > + <p><b>Following lines are a snippet of
> > + <a href="/doc/guides/contributing/patches.html">contribution guidelines</a>,
> > + consult it for more details.</b>
>
> The last line "consult it for more details" is confusing and can be removed.
Right.
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2016-07-27 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 12:15 Nelio Laranjeiro
2016-07-27 12:15 ` [dpdk-web] [PATCH 2/3] add alternative to send another patch version Nelio Laranjeiro
2016-07-27 13:03 ` Thomas Monjalon
2016-07-27 13:25 ` Nélio Laranjeiro
2016-07-27 12:15 ` [dpdk-web] [PATCH 3/3] inform where Message ID can be found Nelio Laranjeiro
2016-07-27 13:22 ` Thomas Monjalon
2016-07-27 13:26 ` Nélio Laranjeiro
2016-07-27 13:01 ` [dpdk-web] [PATCH 1/3] move up contribution guidelines link Thomas Monjalon
2016-07-27 13:24 ` Nélio Laranjeiro [this message]
2016-07-27 13:34 ` [dpdk-web] [PATCH v2 1/2] " Nelio Laranjeiro
2016-07-27 13:34 ` [dpdk-web] [PATCH v2 2/2] inform where Message ID can be found Nelio Laranjeiro
2016-07-27 13:48 ` [dpdk-web] [PATCH v2 1/2] move up contribution guidelines link Thomas Monjalon
2016-07-27 13:51 ` Mcnamara, John
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=20160727132412.GT14792@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@dpdk.org \
/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).