Return-Path: <commits-return-47497-archive-asf-public=cust-asf.ponee.io@directory.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 2BEB4200BFF
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue,  3 Jan 2017 03:40:54 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 2A9D6160B30; Tue,  3 Jan 2017 02:40:54 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 4B929160B22
	for <archive-asf-public@cust-asf.ponee.io>; Tue,  3 Jan 2017 03:40:53 +0100 (CET)
Received: (qmail 76267 invoked by uid 500); 3 Jan 2017 02:40:52 -0000
Mailing-List: contact commits-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@directory.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@directory.apache.org>
List-Post: <mailto:commits@directory.apache.org>
List-Id: <commits.directory.apache.org>
Reply-To: dev@directory.apache.org
Delivered-To: mailing list commits@directory.apache.org
Received: (qmail 76258 invoked by uid 99); 3 Jan 2017 02:40:52 -0000
Received: from Unknown (HELO svn01-us-west.apache.org) (209.188.14.144)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2017 02:40:52 +0000
Received: from svn01-us-west.apache.org (localhost [127.0.0.1])
	by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id EE3303A3AEB
	for <commits@directory.apache.org>; Tue,  3 Jan 2017 02:40:51 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1004017 - in /websites/staging/directory/trunk/content: ./
 apacheds/coding-standards.html api/coding-standards.html
 fortress/coding-standards.html mavibot/coding-standards.html
Date: Tue, 03 Jan 2017 02:40:51 -0000
To: commits@directory.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.9
Message-Id: <20170103024051.EE3303A3AEB@svn01-us-west.apache.org>
archived-at: Tue, 03 Jan 2017 02:40:54 -0000

Author: buildbot
Date: Tue Jan  3 02:40:51 2017
New Revision: 1004017

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/coding-standards.html
    websites/staging/directory/trunk/content/api/coding-standards.html
    websites/staging/directory/trunk/content/fortress/coding-standards.html
    websites/staging/directory/trunk/content/mavibot/coding-standards.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jan  3 02:40:51 2017
@@ -1 +1 @@
-1777053
+1777054

Modified: websites/staging/directory/trunk/content/apacheds/coding-standards.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/coding-standards.html (original)
+++ websites/staging/directory/trunk/content/apacheds/coding-standards.html Tue Jan  3 02:40:51 2017
@@ -162,7 +162,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="coding-standards">Coding Standards<a class="headerlink" href="#coding-standards" title="Permanent link">&para;</a></h1>
-<p>Welcome to you, developer -- you've maybe been elected committer on the project, or want to contribute some code / patch? This is great news! However, in order to be able to share your 'vision' and your code, some rules must be followed.</p>
+<p>Welcome to you fellow developer!  You've maybe been elected committer on the project, or want to contribute some code / patch? This is great news!! However, in order to be able to share your 'vision' with your code, some rules must be followed.</p>
 <p>Hey, remember that those rules are not the best nor the worst, they are pretty much what they are for historical reasons, or for technical reasons, however, please, accept them as they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using spaces instead of tab ??? How stupid is this rule etc etc.) Rules are <em><em>alway</em>s</em> stupid, but smart people follow them ;)</p>
 <p><strong>eclipse IDE</strong></p>
 <p>Eclipse users can import those two files to enfore the code formating : <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/formatting.xml">formatting.xml</a> and <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/codetemplates.xml">codetemplates.xml</a></p>

Modified: websites/staging/directory/trunk/content/api/coding-standards.html
==============================================================================
--- websites/staging/directory/trunk/content/api/coding-standards.html (original)
+++ websites/staging/directory/trunk/content/api/coding-standards.html Tue Jan  3 02:40:51 2017
@@ -165,7 +165,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="coding-standards">Coding Standards<a class="headerlink" href="#coding-standards" title="Permanent link">&para;</a></h1>
-<p>Welcome to you, developer -- you've maybe been elected committer on the project, or want to contribute some code / patch? This is great news! However, in order to be able to share your 'vision' and your code, some rules must be followed.</p>
+<p>Welcome to you fellow developer!  You've maybe been elected committer on the project, or want to contribute some code / patch? This is great news!! However, in order to be able to share your 'vision' with your code, some rules must be followed.</p>
 <p>Hey, remember that those rules are not the best nor the worst, they are pretty much what they are for historical reasons, or for technical reasons, however, please, accept them as they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using spaces instead of tab ??? How stupid is this rule etc etc.) Rules are <em><em>alway</em>s</em> stupid, but smart people follow them ;)</p>
 <p><strong>eclipse IDE</strong></p>
 <p>Eclipse users can import those two files to enfore the code formating : <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/formatting.xml">formatting.xml</a> and <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/codetemplates.xml">codetemplates.xml</a></p>

Modified: websites/staging/directory/trunk/content/fortress/coding-standards.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/coding-standards.html (original)
+++ websites/staging/directory/trunk/content/fortress/coding-standards.html Tue Jan  3 02:40:51 2017
@@ -168,7 +168,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="coding-standards">Coding Standards<a class="headerlink" href="#coding-standards" title="Permanent link">&para;</a></h1>
-<p>Welcome to you, developer -- you've maybe been elected committer on the project, or want to contribute some code / patch? This is great news! However, in order to be able to share your 'vision' and your code, some rules must be followed.</p>
+<p>Welcome to you fellow developer!  You've maybe been elected committer on the project, or want to contribute some code / patch? This is great news!! However, in order to be able to share your 'vision' with your code, some rules must be followed.</p>
 <p>Hey, remember that those rules are not the best nor the worst, they are pretty much what they are for historical reasons, or for technical reasons, however, please, accept them as they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using spaces instead of tab ??? How stupid is this rule etc etc.) Rules are <em><em>alway</em>s</em> stupid, but smart people follow them ;)</p>
 <p><strong>eclipse IDE</strong></p>
 <p>Eclipse users can import those two files to enfore the code formating : <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/formatting.xml">formatting.xml</a> and <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/codetemplates.xml">codetemplates.xml</a></p>

Modified: websites/staging/directory/trunk/content/mavibot/coding-standards.html
==============================================================================
--- websites/staging/directory/trunk/content/mavibot/coding-standards.html (original)
+++ websites/staging/directory/trunk/content/mavibot/coding-standards.html Tue Jan  3 02:40:51 2017
@@ -164,7 +164,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="mavibot-coding-standards">Mavibot Coding Standards<a class="headerlink" href="#mavibot-coding-standards" title="Permanent link">&para;</a></h1>
-<p>Welcome to you, developer -- you've maybe been elected committer on the project, or want to contribute some code / patch? This is great news! However, in order to be able to share your 'vision' and your code, some rules must be followed.</p>
+<p>Welcome to you fellow developer!  You've maybe been elected committer on the project, or want to contribute some code / patch? This is great news!! However, in order to be able to share your 'vision' with your code, some rules must be followed.</p>
 <p>Hey, remember that those rules are not the best nor the worst, they are pretty much what they are for historical reasons, or for technical reasons, however, please, accept them as they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using spaces instead of tab ??? How stupid is this rule etc etc.) Rules are <em><em>alway</em>s</em> stupid, but smart people follow them ;)</p>
 <p><strong>eclipse IDE</strong></p>
 <p>Eclipse users can import those two files to enforce the code formating : <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/formatting.xml">formatting.xml</a> and <a href="http://svn.apache.org/repos/asf/directory/project/trunk/resources/codetemplates.xml">codetemplates.xml</a></p>