-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete stale branches #991
Comments
I'm okay to delete them. I think we should leave open any that are pull requests and just bump those threads separately so we can discuss what to do with each. |
+1 |
Ok, I've deleted some 5 years old branches. |
@berkerpeksag that's awesome! Should we close the ticket or any other branch in mind? |
Deleted some more of my branches. |
I haven't investigate all the branches yet, we can keep this open for a while :) |
right :)i also saw some branches i should take care...
|
bump |
Can we delete the python2.5 and the py24 branches yet? :-P |
I just deleted these branches that were fully merged:
I left feature/tcp_fastopen because it was recently reverted. |
👍 |
@tilgovi totally supporting py26 is already something we should consider to stop imo also... |
I also just deleted fix/1174 and djangoreload branches. The latter is not needed anymore since djangoapp.py will be removed by #1076. |
closing the issue as it seems we are OK with this now. Feel free to reopen the ticket if needed. |
also thanks for the work :) |
There are a lot of stale branches in the repo. I'm not sure they are still useful. Can we delete them?
Here is the list of the stale branches: https://github.com/benoitc/gunicorn/branches/stale
The text was updated successfully, but these errors were encountered: