Lines Matching +full:zfs +full:- +full:tests
4 …src="https://openzfs.github.io/openzfs-docs/_static/img/logo/480px-Open-ZFS-Secondary-Logo-Colour-…
13 started?](#what-should-i-know-before-i-get-started)
15 * [Get ZFS](#get-zfs)
16 * [Debug ZFS](#debug-zfs)
17 * [Where can I ask for help?](#where-can-I-ask-for-help)
19 [How Can I Contribute?](#how-can-i-contribute)
21 * [Reporting Bugs](#reporting-bugs)
22 * [Suggesting Enhancements](#suggesting-enhancements)
23 * [Pull Requests](#pull-requests)
26 [Style Guides](#style-guides)
28 * [Coding Conventions](#coding-conventions)
29 * [Commit Message Formats](#commit-message-formats)
30 * [New Changes](#new-changes)
31 * [OpenZFS Patch Ports](#openzfs-patch-ports)
32 * [Coverity Defect Fixes](#coverity-defect-fixes)
33 * [Signed Off By](#signed-off-by)
37 * [OpenZFS Documentation](https://openzfs.github.io/openzfs-docs/)
38 * [OpenZFS Developer Resources](http://open-zfs.org/wiki/Developer_resources)
39 …* [Git and GitHub for beginners](https://openzfs.github.io/openzfs-docs/Developer%20Resources/Git%…
43 ### Get ZFS
44 You can build zfs packages by following [these
45 instructions](https://openzfs.github.io/openzfs-docs/Developer%20Resources/Building%20ZFS.html),
47 repository](https://openzfs.github.io/openzfs-docs/Getting%20Started/index.html).
49 ### Debug ZFS
50 A variety of methods and tools are available to aid ZFS developers.
51 It's strongly recommended that when developing a patch the `--enable-debug`
56 provide visibility into the inner workings of ZFS. The most useful
58 page](https://openzfs.github.io/openzfs-docs/Basic%20Concepts/Troubleshooting.html).
61 The [zfs-discuss mailing
62 list](https://openzfs.github.io/openzfs-docs/Project%20and%20Community/Mailing%20Lists.html)
69 *Please* contact us via the [zfs-discuss mailing
70 list](https://openzfs.github.io/openzfs-docs/Project%20and%20Community/Mailing%20Lists.html)
74 tracker](https://github.com/openzfs/zfs/issues) *first* to ensure the
79 tracker](https://github.com/openzfs/zfs/issues).
83 * The spl and zfs versions you are using, installation method (repository
107 * Values of the spl/zfs module parameters.
117 label](https://github.com/openzfs/zfs/issues?q=is%3Aopen+is%3Aissue+label%3A%22Type%3A+Feature%22).
134 [Commit Message Formats](#commit-message-formats) section for more information.
136 [rebase](https://git-scm.com/docs/git-rebase) (squash).
147 #### Tests and Benchmarks
148 …d using a GitHub Actions workflow on multiple platforms by running the [zfs-tests.sh and zloop.sh](
149 https://openzfs.github.io/openzfs-docs/Developer%20Resources/Building%20ZFS.html#running-zloop-sh-a…
150 …-ci-type.py` is used to determine whether the pull request is nonbehavior, i.e., not introducing b…
151 …* If your last commit (or `HEAD` in git terms) contains a line `ZFS-CI-Type: quick`, quick mode is…
152 * Otherwise, if any commit in a PR contains a line `ZFS-CI-Type: full`, full mode is forced.
154 https://github.com/openzfs/zfs/blob/master/.github/CONTRIBUTING.md#style-guides
168 Users can also run the [ZFS Test
169 Suite](https://github.com/openzfs/zfs/tree/master/tests) on their systems
170 to verify ZFS is behaving as intended.
177 - The "development and main branch", is the branch all development should be based on.
178 - "Release branches" contain the latest released code for said version.
179 - "Staging branches" contain selected commits prior to being released.
182 - Development and Main branch: `master`
183 - Release branches: `zfs-$VERSION-release`
184 - Staging branches: `zfs-$VERSION-staging`
201 git config --local core.whitespace trailing-space,space-before-tab,indent-with-non-tab,-tab-in-inde…
213 * The last line must be a `Signed-off-by:` tag. See the
214 [Signed Off By](#signed-off-by) section for more information.
226 Signed-off-by: Contributor <contributor@email.com>
231 [Coverity defect](https://scan.coverity.com/projects/zfsonlinux-zfs),
237 * The last line must be a `Signed-off-by:` tag. See the
238 [Signed Off By](#signed-off-by) section for more information.
253 Signed-off-by: Contributor <contributor@email.com>
257 A line tagged as `Signed-off-by:` must contain the developer's
261 ….kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certifi…
264 Git can append the `Signed-off-by` line to your commit messages. Simply
265 provide the `-s` or `--signoff` option when performing a `git commit`.
267 a Git Commit Message](https://chris.beams.io/posts/git-commit/).
269 #### Co-authored By
271 `Co-authored-by: Name <gitregistered@email.address>`
273 but may be used in any situation where there are co-authors.
277 `Co-authored-by: Name <[username]@users.noreply.github.com>`