@@ -108,7 +108,7 @@ request is merged you could change your `path` dependency to:
108
108
109
109
``` toml
110
110
[patch .crates-io ]
111
- uuid = { git = ' https://github.com/uuid-rs/uuid' }
111
+ uuid = { git = ' https://github.com/uuid-rs/uuid.git ' }
112
112
```
113
113
114
114
[ uuid-repository ] : https://github.com/uuid-rs/uuid
@@ -135,7 +135,7 @@ version = "0.1.0"
135
135
uuid = " 1.0.1"
136
136
137
137
[patch .crates-io ]
138
- uuid = { git = ' https://github.com/uuid-rs/uuid' }
138
+ uuid = { git = ' https://github.com/uuid-rs/uuid.git ' }
139
139
```
140
140
141
141
Note that our local dependency on ` uuid ` has been updated to ` 1.0.1 ` as it's
@@ -161,7 +161,7 @@ my-library = { git = 'https://example.com/git/my-library' }
161
161
uuid = " 1.0"
162
162
163
163
[patch .crates-io ]
164
- uuid = { git = ' https://github.com/uuid-rs/uuid' }
164
+ uuid = { git = ' https://github.com/uuid-rs/uuid.git ' }
165
165
```
166
166
167
167
Remember that ` [patch] ` is applicable * transitively* but can only be defined at
@@ -197,7 +197,7 @@ we've submitted all changes upstream we can update our manifest for
197
197
uuid = " 2.0"
198
198
199
199
[patch .crates-io ]
200
- uuid = { git = " https://github.com/uuid-rs/uuid" , branch = " 2.0.0" }
200
+ uuid = { git = " https://github.com/uuid-rs/uuid.git " , branch = " 2.0.0" }
201
201
```
202
202
203
203
And that's it! Like with the previous example the 2.0.0 version doesn't actually
@@ -215,7 +215,7 @@ my-library = { git = 'https://example.com/git/my-library' }
215
215
uuid = " 1.0"
216
216
217
217
[patch .crates-io ]
218
- uuid = { git = ' https://github.com/uuid-rs/uuid' , branch = ' 2.0.0' }
218
+ uuid = { git = ' https://github.com/uuid-rs/uuid.git ' , branch = ' 2.0.0' }
219
219
```
220
220
221
221
Note that this will actually resolve to two versions of the ` uuid ` crate. The
@@ -234,8 +234,8 @@ configure this we'd do:
234
234
235
235
``` toml
236
236
[patch .crates-io ]
237
- serde = { git = ' https://github.com/serde-rs/serde' }
238
- serde2 = { git = ' https://github.com/example/serde' , package = ' serde' , branch = ' v2' }
237
+ serde = { git = ' https://github.com/serde-rs/serde.git ' }
238
+ serde2 = { git = ' https://github.com/example/serde.git ' , package = ' serde' , branch = ' v2' }
239
239
```
240
240
241
241
The first ` serde = ... ` directive indicates that serde ` 1.* ` should be used
@@ -256,14 +256,14 @@ with other copies. The syntax is similar to the
256
256
257
257
``` toml
258
258
[patch .crates-io ]
259
- foo = { git = ' https://github.com/example/foo' }
259
+ foo = { git = ' https://github.com/example/foo.git ' }
260
260
bar = { path = ' my/local/bar' }
261
261
262
262
[dependencies .baz ]
263
- git = ' https://github.com/example/baz'
263
+ git = ' https://github.com/example/baz.git '
264
264
265
265
[patch .'https://github .com/example/baz' ]
266
- baz = { git = ' https://github.com/example/patched-baz' , branch = ' my-branch' }
266
+ baz = { git = ' https://github.com/example/patched-baz.git ' , branch = ' my-branch' }
267
267
```
268
268
269
269
> ** Note** : The ` [patch] ` table can also be specified as a [ configuration
@@ -305,7 +305,7 @@ copies. The syntax is similar to the `[dependencies]` section:
305
305
306
306
``` toml
307
307
[replace ]
308
- "foo:0.1.0" = { git = ' https://github.com/example/foo' }
308
+ "foo:0.1.0" = { git = ' https://github.com/example/foo.git ' }
309
309
"bar:1.0.2" = { path = ' my/local/bar' }
310
310
```
311
311
0 commit comments