-
Notifications
You must be signed in to change notification settings - Fork 7
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 legacy2016 branch? #70
Comments
Hi Yongbin,
do you mean merge the legacy2016 with master, and then remove the branch? Best,
Alberto
From: Yongbin Feng<mailto:notifications@github.com>
Sent: Sunday, May 5, 2019 9:12 PM
To: albertobelloni/WG_Analysis<mailto:WG_Analysis@noreply.github.com>
Cc: Subscribed<mailto:subscribed@noreply.github.com>
since everyone is using legacy2016 now I would propose we delete the legacy2016 branch and keep track of master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#70>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABAO3DRBGBFTV7CPOYYEY2TPT6ATZANCNFSM4HK4SW3Q>.
|
ah sorry for the confusion. Legacy2016 has been merged to the master branch already. Just in case anyone is still on legacy2016, it might be good to switch to master and sync? (Not urgent) |
Moved to master, and abandoned legacy2016 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
since everyone is using legacy2016 now I would propose we delete the legacy2016 branch and keep track of master.
The text was updated successfully, but these errors were encountered: