summaryrefslogtreecommitdiff
path: root/README.GIT-RULES
diff options
context:
space:
mode:
authorStanislav Malyshev <stas@php.net>2018-07-31 12:44:51 -0700
committerStanislav Malyshev <stas@php.net>2018-07-31 12:44:51 -0700
commit65167f1c7d5a087022270b8b8fe10a3b0c58b3a0 (patch)
tree2e5240f032d7df4edafa7f10eda802680b5267ba /README.GIT-RULES
parent201022c34791318034f37591d00a39fc00577654 (diff)
downloadphp-git-65167f1c7d5a087022270b8b8fe10a3b0c58b3a0.tar.gz
[ci skip] Ugh, whitespace
Diffstat (limited to 'README.GIT-RULES')
-rw-r--r--README.GIT-RULES8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.GIT-RULES b/README.GIT-RULES
index 591b56b162..a2dfb6aeab 100644
--- a/README.GIT-RULES
+++ b/README.GIT-RULES
@@ -79,10 +79,10 @@ Currently we have the following branches in use::
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
+ 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
which were dropped from later branches) an empty merge should be done.
2. All news updates intended for public viewing, such as new features,