mirror of
https://git.proxmox.com/git/mirror_zfs.git
synced 2024-12-26 19:19:32 +03:00
fda0f16217
It's often necessary to understand why a change is made, before understanding the exact changes that are made. Context provides background, which by definition is necessary to understand prior to the substance of the Pull Request. Change the PR template to request "Motivation and Context" first, before "Description". Reviewed-by: Giuseppe Di Natale <guss80@gmail.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Matthew Ahrens <mahrens@delphix.com> Closes #7737
2.1 KiB
2.1 KiB
Motivation and Context
Description
How Has This Been Tested?
Types of changes
- 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:
- My code follows the ZFS on Linux code style requirements.
- I have updated the documentation accordingly.
- I have read the contributing document.
- I have added tests to cover my changes.
- All new and existing tests passed.
- All commit messages are properly formatted and contain
Signed-off-by. - Change has been approved by a ZFS on Linux member.