]>
Commit | Line | Data |
---|---|---|
d57f03e4 GM |
1 | <!--- Provide a general summary of your changes in the Title above --> |
2 | ||
3 | ### Description | |
4 | <!--- Describe your changes in detail --> | |
5 | ||
6 | ### Motivation and Context | |
7 | <!--- Why is this change required? What problem does it solve? --> | |
8 | <!--- If it fixes an open issue, please link to the issue here. --> | |
9 | ||
10 | ### How Has This Been Tested? | |
11 | <!--- Please describe in detail how you tested your changes. --> | |
12 | <!--- Include details of your testing environment, and the tests you ran to --> | |
13 | <!--- see how your change affects other areas of the code, etc. --> | |
14 | <!--- If your change is a performance enhancement, please provide benchmarks here. --> | |
15 | ||
16 | ### Types of changes | |
17 | <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> | |
18 | - [ ] Bug fix (non-breaking change which fixes an issue) | |
19 | - [ ] New feature (non-breaking change which adds functionality) | |
20 | - [ ] Performance enhancement (non-breaking change which improves efficiency) | |
21 | - [ ] Code cleanup (non-breaking change which makes code smaller or more readable) | |
22 | - [ ] Breaking change (fix or feature that would cause existing functionality to change) | |
23 | ||
24 | ### Checklist: | |
25 | <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> | |
26 | <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> | |
27 | - [ ] My code follows the ZFS on Linux code style requirements. | |
28 | - [ ] I have updated the documentation accordingly. | |
29 | - [ ] I have read the **CONTRIBUTING** document. | |
30 | - [ ] I have added tests to cover my changes. | |
31 | - [ ] All new and existing tests passed. | |
32 | - [ ] Change has been approved by a ZFS on Linux member. |