com php-src: [ci skip] Typo: README.GIT-RULES
| From: | Stanislav Malyshev | Date: | Wed, 01 Aug 2018 05:41:11 +0000 |
| Subject: | com php-src: [ci skip] Typo: README.GIT-RULES | ||
| Groups: | php.cvs | ||
| Request: | Send a blank email to php-cvs+get-102766@lists.php.net to get a copy of this message | ||
Commit: 3ea095ab00c6106755590ccd659e6e0de3e53a00
Author: Stanislav Malyshev <stas@php.net> Tue, 31 Jul 2018 22:40:21 -0700
Parents: 65167f1c7d5a087022270b8b8fe10a3b0c58b3a0
Branches: master
Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=3ea095ab00c6106755590ccd659e6e0de3e53a00
Log:
[ci skip] Typo
Changed paths:
M README.GIT-RULES
Diff:
diff --git a/README.GIT-RULES b/README.GIT-RULES
index a2dfb6a..e4a04ff 100644
--- a/README.GIT-RULES
+++ b/README.GIT-RULES
@@ -82,7 +82,7 @@ The next few rules are more of a technical nature::
1. All non-security bugfix changes should first go to the lowest bugfix
branch (i.e. 7.1) and then get merged up to all other branches.
All security fixes should go to the lowest security fixes branch (i.e 5.6).
- If a change is not needed for ater branches (i.e. fixes for features
+ If a change is not needed for later branches (i.e. fixes for features
which were dropped from later branches) an empty merge should be done.
2. All news updates intended for public viewing, such as new features,