summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2021-03-23 10:27:13 +0900
committerYuki Okushi <huyuumi.dev@gmail.com>2021-03-23 10:27:13 +0900
commit52956ae8f8395d69af59f1d3ad751b03c39d24db (patch)
tree658cdc269b8b2624a74be3a0f167a9cb20113963 /CONTRIBUTING.md
parent765cca1fe2603b4838c0fcd741b5334becf0cda8 (diff)
downloadrust-libc-52956ae8f8395d69af59f1d3ad751b03c39d24db.tar.gz
Mention about `libc-test` on the publishing note
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1acc71d9ca..5d52cad7fc 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -69,11 +69,11 @@ platform in this crate, the next step is to get that sweet, sweet usage from
crates.io! The only next step is to bump the version of libc and then publish
it. If you'd like to get a release out ASAP you can follow these steps:
-1. Increment the patch version number in `Cargo.toml`.
-1. Send a PR to this repository. It should [look like this][example], but it'd
+1. Increment the patch version number in `Cargo.toml` and `libc-test/Cargo.toml`.
+1. Send a PR to this repository. It should [look like this][example-pr], but it'd
also be nice to fill out the description with a small rationale for the
release (any rationale is ok though!)
1. Once merged, the release will be tagged and published by one of the libc crate
maintainers.
-[example]: https://github.com/rust-lang/libc/pull/583
+[example-pr]: https://github.com/rust-lang/libc/pull/2120