[Rt-commit] rt branch, 4.0-trunk, updated. rt-4.0.5-81-g0ebc9d4

[Thomas Sibley]

The branch, 4.0-trunk has been updated
       via  0ebc9d4b071fd1f4d08b977b6421b124d82f4e55 (commit)
      from  2d50c9ee79af79763360190b4a62180628cc6f0f (commit)

Summary of changes:
 docs/hacking.pod |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

- Log -----------------------------------------------------------------
commit 0ebc9d4b071fd1f4d08b977b6421b124d82f4e55
Author: ashley willis <ashleywillis76 at gmail.com>
Date:   Thu Mar 8 04:21:58 2012 -0600

    corrected "to be passing always be passing" --> "to always be passing" in docs/hacking.pod.
    
    Signed-off-by: Thomas Sibley <trs at bestpractical.com>

diff --git a/docs/hacking.pod b/docs/hacking.pod
index 8aa84fd..396c562 100644
--- a/docs/hacking.pod
+++ b/docs/hacking.pod
@@ -186,11 +186,11 @@ which will be significantly faster:
 
     make test-parallel
 
-The C<*-trunk> and C<master> branches are expected to be passing always
-be passing all tests.  While it is acceptable to break tests in an
-intermediate commit, a branch which does not pass tests will not be
-merged.  Ideally, commits which fix a bug should also include a testcase
-which fails before the fix and succeeds after.
+The C<*-trunk> and C<master> branches are expected to always be passing
+all tests.  While it is acceptable to break tests in an intermediate
+commit, a branch which does not pass tests will not be merged.  Ideally,
+commits which fix a bug should also include a testcase which fails
+before the fix and succeeds after.
 
 
 

-----------------------------------------------------------------------