com php-src: Fix typos in git rules and release process READMEs: README.GIT-RULES README.RELEASE_PROCESS
| From: | Nikita Popov | Date: | Fri, 29 Jan 2016 16:04:39 +0000 |
| Subject: | com php-src: Fix typos in git rules and release process READMEs: README.GIT-RULES README.RELEASE_PROCESS | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-90812@lists.php.net to get a copy of this message | ||
Commit: c7c1679bb36df048a3e0c3a25c1d7a8e48c1e897
Author: Prayag Verma <prayag.verma@gmail.com> Thu, 28 Jan 2016 19:50:35 +0530
Committer: Nikita Popov <nikic@php.net> Fri, 29 Jan 2016 17:04:39 +0100
Parents: 1c709f08c7e404cac8544dcb2fa2df285f832ffb
Branches: master
Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=c7c1679bb36df048a3e0c3a25c1d7a8e48c1e897
Log:
Fix typos in git rules and release process READMEs
Changed paths:
M README.GIT-RULES
M README.RELEASE_PROCESS
Diff:
diff --git a/README.GIT-RULES b/README.GIT-RULES
index 5f35cc4..a88a8c9 100644
--- a/README.GIT-RULES
+++ b/README.GIT-RULES
@@ -79,7 +79,7 @@ The next few rules are more of a technical nature::
should be noted in both PHP-5.4/NEWS and PHP-5.5/NEWS but
not master, which is not a public released version yet.
- 3. Do not commit multiple file and dump all messages in one commit. If you
+ 3. Do not commit multiple files and dump all messages in one commit. If you
modified several unrelated files, commit each group separately and
provide a nice commit message for each one. See example below.
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index 38bc6e1..3411ed9 100644
--- a/README.RELEASE_PROCESS
+++ b/README.RELEASE_PROCESS
@@ -17,7 +17,7 @@ It is recommended to do so a couple of days before the packaging day, to
have enough time to investigate failures, communicate with the authors and
commit the fixes.
The RM for the branch is also responsible for keeping the CI green on
-ongoing bases between the releases. Check the CI status for your branch
+ongoing basis between the releases. Check the CI status for your branch
periodically and resolve the failures ASAP. See more in:
https://wiki.php.net/rfc/travis_ci
@@ -271,8 +271,8 @@ to upgrade.
10. Wait an hour or two, then send a mail to php-announce@lists.php.net,
php-general@lists.php.net and internals@lists.php.net with a text similar to
http://news.php.net/php.internals/17222.
-Please make sure that the mail to php-announce@ is its own completely seperate email.
-This is to make sure that repiles to the announcement on php-general@ or internals@
+Please make sure that the mail to php-announce@ is its own completely separate email.
+This is to make sure that replies to the announcement on php-general@ or internals@
will not accidentally hit the php-announce@ mailinglist.
Re-releasing the same version (or -pl)
@@ -309,6 +309,6 @@ to upgrade.
5. Wait an hour or two, then send a mail to php-announce@lists.php.net,
php-general@lists.php.net and internals@lists.php.net with a text similar to
the news entry.
-Please make sure that the mail to php-announce@ is its own completely seperate email.
-This is to make sure that repiles to the announcement on php-general@ or internals@
+Please make sure that the mail to php-announce@ is its own completely separate email.
+This is to make sure that replies to the announcement on php-general@ or internals@
will not accidentally hit the php-announce@ mailinglist.