summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorPhilipp Gesang <phg@phi-gamma.net>2019-09-12 11:33:57 +0200
committerPhilipp Gesang <phg@phi-gamma.net>2019-09-18 23:31:33 +0200
commit9a09cb4ff31afc8ff857780be321273f240a3da5 (patch)
tree2ac2f63118cea9ec172dcbf26ef06dcb9ae6804e /CONTRIBUTING.md
parent165161bec33eda2e0b614ca464cacb2a4079b1b3 (diff)
downloadrust-libc-9a09cb4ff31afc8ff857780be321273f240a3da5.tar.gz
update example path
Signed-off-by: Philipp Gesang <phg@phi-gamma.net>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7c22c08622..052777f416 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -21,7 +21,7 @@ Consequently, this indicates where an API should be added! Adding an API at a
particular level in the hierarchy means that it is supported on all the child
platforms of that level. For example, when adding a Unix API it should be added
to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
-`src/unix/notbsd/linux/mod.rs`.
+`src/unix/linux_like/linux/mod.rs`.
If you're not 100% sure at what level of the hierarchy an API should be added
at, fear not! This crate has CI support which tests any binding against all