From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
To: web@dpdk.org
Cc: thomas.monjalon@6wind.com
Subject: [dpdk-web] [PATCH v2 1/2] move up contribution guidelines link
Date: Wed, 27 Jul 2016 15:34:34 +0200 [thread overview]
Message-ID: <1469626475-8996-1-git-send-email-nelio.laranjeiro@6wind.com> (raw)
In-Reply-To: <1469621722-754-1-git-send-email-nelio.laranjeiro@6wind.com>
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 may fail.
Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
---
dev.html | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/dev.html b/dev.html
index cb65f51..9a01ab5 100644
--- a/dev.html
+++ b/dev.html
@@ -57,6 +57,9 @@
<p>Focus is on next version in git <em>HEAD</em>. There is no maintenance of previous versions.
<h3 id="send">Contribute by sending patches</h3>
+ <p><b>Following lines are a snippet of
+ <a href="/doc/guides/contributing/patches.html">contribution guidelines</a>.</b>
+
<p>Patches should be sent and reviewed via the <a href="/ml/archives/dev">mailing list</a>.
Be sure <a href="/ml/listinfo/dev">to be registered</a>.
<p>To prepare a patch, it must be saved with
@@ -105,8 +108,6 @@
smtpencryption = ssl
[alias]
fixline = log -1 --abbrev=12 --format='Fixes: %h (\"%s\")'</pre>
- <p>The built-in documentation have more details about the
- <a href="/doc/guides/contributing/patches.html">contribution guidelines</a>.
<h3 id="review">Contribute by testing or reviewing patches</h3>
<p>Patches are applied in the git repository when it becomes clear that
--
2.1.4
next prev parent reply other threads:[~2016-07-27 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 12:15 [dpdk-web] [PATCH 1/3] " 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
2016-07-27 13:34 ` Nelio Laranjeiro [this message]
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=1469626475-8996-1-git-send-email-nelio.laranjeiro@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).