test: copy files in test_expect_equal_file instead of moving them

[notmuch] / RELEASING

diff --git a/RELEASING b/RELEASING
index e9cb3d0bfbe2040dcf46a4edcee1f6086ebb6ef2..a392d819f9cc8ca2ad262c609c47ffcb2b712fe7 100644 (file)
--- a/RELEASING
+++ b/RELEASING
@@ -13,7 +13,7 @@ repository. From here, there are just a few steps to release:
 
        Read through the entry at the top of the NEWS file and see if
        you are aware of any major features recently added that are
 
        Read through the entry at the top of the NEWS file and see if
        you are aware of any major features recently added that are

-       not mentioned there. If so, pleas add them, (and ask the
+       not mentioned there. If so, please add them, (and ask the

        authors of the commits to update NEWS in the future).
 
 2) Verify that the library version in lib/Makefile.local is correct
        authors of the commits to update NEWS in the future).
 
 2) Verify that the library version in lib/Makefile.local is correct


@@ -48,10 +48,10 @@ repository. From here, there are just a few steps to release:
        as "1.1" or "1.2").
 
        Finally, releases that do not change "features" but are merely
        as "1.1" or "1.2").
 
        Finally, releases that do not change "features" but are merely

-       bug fixes either add increase the micro number or add it
-       (starting at ".1" if not present). So a bug-fix release from
-       "1.0" would be "1.0.1" and a subsequent bug-fix release would
-       be "1.0.2" etc.
+       bug fixes either increase the micro number or add it (starting
+       at ".1" if not present). So a bug-fix release from "1.0" would
+       be "1.0.1" and a subsequent bug-fix release would be "1.0.2"
+       etc.

 
        Commit this change.
 
 
        Commit this change.