Information for RPM git-publish-1.6.1-2.fc33.src.rpm
| ID | 650181 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Name | git-publish | ||||||||
| Version | 1.6.1 | ||||||||
| Release | 2.fc33 | ||||||||
| Epoch | |||||||||
| Arch | src | ||||||||
| Summary | Prepare and store patch revisions as git tags | ||||||||
| Description | git-publish handles repetitive and time-consuming details of managing patch email submission. It works with individual patches as well as patch series and has support for pull request emails. Each revision is stored as a git tag including the cover letter (if any). This makes it easy to refer back to previous revisions of a patch. Numbering is handled automatically and the To:/Cc: email addresses are remembered across revisions to save you retyping them. Many projects have conventions for submitting patches. It is possible to encode them as a .gitpublish file and hooks/ scripts. This automatically uses the right settings and can run a coding style checker or linting tools before emails are sent. | ||||||||
| Build Time | 2020-07-27 23:32:13 GMT | ||||||||
| Size | 31.49 KB | ||||||||
| 488f59f3c6aff97b0811c63ca671efab | |||||||||
| License | MIT | ||||||||
| Provides |
|
||||||||
| Obsoletes | No Obsoletes | ||||||||
| Conflicts | No Conflicts | ||||||||
| Requires |
|
||||||||
| Recommends | No Recommends | ||||||||
| Suggests | No Suggests | ||||||||
| Supplements | No Supplements | ||||||||
| Enhances | No Enhances | ||||||||
| Files |
|
||||||||
| Component of | No Buildroots | ||||||||
