super_stack 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/README.md +2 -0
- data/lib/super_stack/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: c4e580db536cf127c7e92fd2e9644a3940270179
|
|
4
|
+
data.tar.gz: 6ca39a7b1763c79731f76ec420c074794d334667
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cc98e8fad596daa02f89e3301a108ccb023e0f89b4c569676e7b410d40f79ee1676dd6b2ea683ef85e0fd809753707ca296555a1dc82cace39ed2a71ada66d39
|
|
7
|
+
data.tar.gz: cdf6180b1621fc8fc1a169915d1de62cfad89a5a930ac4af0d9a0eba28630a0fd1bb9293a495c015d57bcd18475f95a89dcf17b3c9281057ec305105120d6469
|
data/README.md
CHANGED
|
@@ -112,6 +112,8 @@ process will use the `default_merge_policy` except if a layer specifies its own.
|
|
|
112
112
|
|
|
113
113
|
In most cases you will just have to set the merge policy at the manager level using `default_merge_policy=`.
|
|
114
114
|
|
|
115
|
+
The alternative is to set the policy at the layer level using `merge_policy=`
|
|
116
|
+
|
|
115
117
|
## Contributing
|
|
116
118
|
|
|
117
119
|
1. Fork it ( http://github.com/lbriais/super_stack/fork )
|
data/lib/super_stack/version.rb
CHANGED