diff --git a/Cargo.toml b/Cargo.toml index 5d96ced..4d95e46 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -8,5 +8,5 @@ resolver = "3" edition = "2024" # crates.io has each member's name, so none is published. publish = false -repository = "https://github.com/moq-dev/rind-patch" +repository = "https://github.com/kixel-ai/rind-patch" license = "Apache-2.0 OR ISC OR MIT-0" diff --git a/README.md b/README.md index ff08222..43c0280 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # rind-patch Crates under the names of crates.io crates, re-exporting -[rind](https://github.com/moq-dev/rind)'s adapters, so that a binary's +[rind](https://github.com/kixel-ai/rind)'s adapters, so that a binary's `[patch.crates-io]` moves its whole dependency tree onto rind. None is published, since crates.io has each name. @@ -13,7 +13,7 @@ ring in its workspace's root `Cargo.toml`, then runs `cargo update -p ring`: ```toml [patch.crates-io] -ring = { git = "https://github.com/moq-dev/rind-patch" } +ring = { git = "https://github.com/kixel-ai/rind-patch" } ``` Every crate in the tree on ring 0.17 then builds rind-ring, including @@ -23,7 +23,7 @@ such as for an exact requirement like `=0.17.14` or before the lockfile is updated, Cargo builds crates.io's ring and only warns, so check that `cargo tree -i ring` prints `ring v0.17.999` from this repository alone. -rind-ring's [README](https://github.com/moq-dev/rind/blob/main/rind-ring/README.md) +rind-ring's [README](https://github.com/kixel-ai/rind/blob/main/rind-ring/README.md) lists what it leaves out and what behaves differently from ring. rind's own CI builds and runs a fixture through this patch, with rind-ring