-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can we delete remaining branched #85
Comments
Why, are they bothering you?
|
you can delete my OperationsRecreation branch if you want. On Wed, Mar 18, 2015 at 11:03 AM, James notifications@github.com wrote:
|
kind of, I am trying to understand if these are legitimate items being worked, if they still need to be worked, if they are already done and in master. etc. They are extremely stale, and haven't been updated in a while, so if they are garbage or OBE, I would like them to be removed. If they are legitimate, then major rebasing needs to be done and we can assign kids to complete them. Are these things for RIDE or not? You deleted certain branches after PVDE but left these, which begs the question, why? Is there code in these branches we still need to develop? |
@ExcelledProducts @jcorcoran
Can we delete the other branches in this repo? Particularly the feature/Calibrating_MotorControllersRevised , lift_hardstop_overshoot_JMC, and operationsRecreation branches
The text was updated successfully, but these errors were encountered: