mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2024-11-17 10:01:01 +03:00
82e996c261
- Splits PR advice into two sections. - Add "co-authored-by" instructions. - Add description of draft PR and when using it is appropriate. - Reword ZFS Test Suite checklist question. - Link to zfs-tests.sh and zloop.sh. Reviewed-By: Marcel Schilling <marcel.schilling@mdc-berlin.de> Reviewed-By: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-By: Richard Laager <rlaager@wiktel.com> Co-Authored-By: Marcel Schilling <marcel.schilling@mdc-berlin.de> Co-Authored-By: Brian Behlendorf <behlendorf1@llnl.gov> Co-Authored-By: Richard Laager <rlaager@wiktel.com> Signed-off-by: Kjeld Schouten-Lebbing <kjeld@schouten-lebbing.nl> Closes #9753
42 lines
2.3 KiB
Markdown
42 lines
2.3 KiB
Markdown
<!--- Please fill out the following template, which will help other contributors review your Pull Request. -->
|
|
|
|
<!--- Provide a general summary of your changes in the Title above -->
|
|
|
|
<!---
|
|
Documentation on ZFS Buildbot options can be found at
|
|
https://github.com/zfsonlinux/zfs/wiki/Buildbot-Options
|
|
-->
|
|
|
|
### Motivation and Context
|
|
<!--- Why is this change required? What problem does it solve? -->
|
|
<!--- If it fixes an open issue, please link to the issue here. -->
|
|
|
|
### Description
|
|
<!--- Describe your changes in detail -->
|
|
|
|
### How Has This Been Tested?
|
|
<!--- Please describe in detail how you tested your changes. -->
|
|
<!--- Include details of your testing environment, and the tests you ran to -->
|
|
<!--- see how your change affects other areas of the code, etc. -->
|
|
<!--- If your change is a performance enhancement, please provide benchmarks here. -->
|
|
<!--- Please think about using the draft PR feature if appropriate -->
|
|
|
|
### Types of changes
|
|
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
|
|
- [ ] Bug fix (non-breaking change which fixes an issue)
|
|
- [ ] New feature (non-breaking change which adds functionality)
|
|
- [ ] Performance enhancement (non-breaking change which improves efficiency)
|
|
- [ ] Code cleanup (non-breaking change which makes code smaller or more readable)
|
|
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
|
|
- [ ] Documentation (a change to man pages or other documentation)
|
|
|
|
### Checklist:
|
|
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
|
|
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
|
|
- [ ] My code follows the ZFS on Linux [code style requirements](https://github.com/zfsonlinux/zfs/blob/master/.github/CONTRIBUTING.md#coding-conventions).
|
|
- [ ] I have updated the documentation accordingly.
|
|
- [ ] I have read the [**contributing** document](https://github.com/zfsonlinux/zfs/blob/master/.github/CONTRIBUTING.md).
|
|
- [ ] I have added [tests](https://github.com/zfsonlinux/zfs/tree/master/tests) to cover my changes.
|
|
- [ ] I have run the ZFS Test Suite with this change applied.
|
|
- [ ] All commit messages are properly formatted and contain [`Signed-off-by`](https://github.com/zfsonlinux/zfs/blob/master/.github/CONTRIBUTING.md#signed-off-by).
|