0
I Use This!
Inactive
Analyzed 1 day ago. based on code collected 1 day ago.

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.

Tags

git patch python

In a Nutshell, smart-patcher...

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...

  • ...
    there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
  • ...
    learn about Open Hub updates and features on the Open Hub blog
  • ...
    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

30 Day Summary

May 31 2022 — Jun 30 2022

12 Month Summary

Jun 30 2021 — Jun 30 2022

Ratings

Be the first to rate this project
Click to add your rating
  
Review this Project!