diff options
| author | Filipe Brandenburger <filbranden@google.com> | 2018-09-07 01:02:42 -0700 |
|---|---|---|
| committer | Filipe Brandenburger <filbranden@google.com> | 2018-09-08 13:39:03 -0700 |
| commit | 9e825ebf4f5029ae6cb072ac568d7838e0762a9e (patch) | |
| tree | 4950d3f39fa29f8513a797d313ca6b48fd04c131 /.github | |
| parent | 9d0798a2edf05438499c7cb5def592d52358f397 (diff) | |
| download | systemd-9e825ebf4f5029ae6cb072ac568d7838e0762a9e.tar.gz | |
docs: move doc/ to docs/
The docs/ directory is special in GitHub, since it can be used to serve GitHub
Pages from, so there's a benefit to switching to it in order to expose it
directly as a website.
Updated references to it from the documentations themselves, from the
CONTRIBUTING.md file and from Meson build files.
Diffstat (limited to '.github')
| -rw-r--r-- | .github/CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 2f266f2934..ea15325fe9 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -24,8 +24,8 @@ If you discover a security vulnerability, we'd appreciate a non-public disclosur ## Posting Pull Requests * Make sure to post PRs only relative to a very recent git master. -* Follow our [Coding Style](https://raw.githubusercontent.com/systemd/systemd/master/doc/CODING_STYLE) when contributing code. This is a requirement for all code we merge. -* Please make sure to test your change before submitting the PR. See [HACKING](https://raw.githubusercontent.com/systemd/systemd/master/doc/HACKING) for details how to do this. +* Follow our [Coding Style](https://raw.githubusercontent.com/systemd/systemd/master/docs/CODING_STYLE) when contributing code. This is a requirement for all code we merge. +* Please make sure to test your change before submitting the PR. See [HACKING](https://raw.githubusercontent.com/systemd/systemd/master/docs/HACKING) for details how to do this. * Make sure to run the test suite locally, before posting your PR. We use a CI system, meaning we don't even look at your PR, if the build and tests don't pass. * If you need to update the code in an existing PR, force-push into the same branch, overriding old commits with new versions. * After you have pushed a new version, add a comment about the new version (no notification is sent just for the commits, so it's easy to miss the update without an explicit comment). If you are a member of the systemd project on GitHub, remove the `reviewed/needs-rework` label. |