dtk-common 0.7.3 → 0.7.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +2 -1
- data/lib/dtk-common/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 6ed78996d908cdeb8b5ffee6415a39593c2ada41
|
4
|
+
data.tar.gz: bb7e95d4eadcaab944540beb0928a61d46dd23a4
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 53b9f73cfcb540eea0eba0f47d65afd72a6fb948a525609d33bf90e994fdcb1726edba04b321475ff2a859ad3292c8d63c007be09b71d4c7ec096ab9c6dd58c0
|
7
|
+
data.tar.gz: 9b12c43d05d7a2e7633c8f9699da70ccd86914c233abda11996de37739cc92a00160a3d94236a0d95088606df1bfaf3b0041704a16128a7e541462c15f3a0d30
|
data/README.md
CHANGED
@@ -9,7 +9,8 @@ GITOLITE
|
|
9
9
|
|
10
10
|
Manager takes responsibility of handling all gitolite methods (or at least most of them). Reason is simple, gitolite commit / push are expensive operations and we want to mitigate that fact by using manager, and making sure that all our changes are under one commit / push.
|
11
11
|
|
12
|
-
|
12
|
+
|
13
|
+
Example: Adding user/user group/all to repo configuration
|
13
14
|
|
14
15
|
manager = Gitolite::Manager.new('/home/git/gitolite-admin')
|
15
16
|
|
data/lib/dtk-common/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: dtk-common
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.7.
|
4
|
+
version: 0.7.4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Rich PELAVIN
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2015-
|
11
|
+
date: 2015-05-20 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: rugged
|