Project Summary
I started this project in order to be able to manage patch emails. I did not want to have to manage them manually but rather wanted it to be as much automated as it could be. Thus started this project.
What it is intended to do is - POP emails, check for PATCH mails, make a chain out of the patches (currently depending on REFERENCES header added by git's send-email), find the spring point of the series, make a new branch amend the patches and send the maintainer a summary report notifying about the amends. Maintainer then should be able to send emails to the patch manager notifying it to rename, merge, delete, push them. Plus the manager will have feature of deleting a branch that the maintainer never worked on after its inception for a specified time period.
In a Nutshell, smart-patcher...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in September, 2008
ending with its most recent commit about 17 years ago
Quick Reference
GNU General Public License v3.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Use Patent Claims
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
Include Install Instructions
These details are provided for information only. No information here is legal advice and should not be used as such.
This Project has No vulnerabilities Reported Against it
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
-
...
use of OSS increased in 65% of companies in 2016
-
...
check out hot projects on the Open Hub
30 Day SummaryNov 8 2025 — Dec 8 2025
|
12 Month SummaryDec 8 2024 — Dec 8 2025
|
