I'm done from android-api branch. We can close this branch. BR, Uze Choi -----Original Message----- From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Jon A. Cruz Sent: Friday, May 22, 2015 6:57 AM To: iotivity-dev at lists.iotivity.org; Keane, Erich Subject: Re: [dev] removal of the android_api branch
On 05/21/2015 11:54 AM, Kourt, Tim A wrote: > Hi All, > > To eliminate any further confusion, we would like to delete the android_api branch as it is no longer properly maintained. > > Uze, please let Pat, Erich know once you are done with it and it can be safely deleted. > Hi, In general I like to see history preserved in SCM, especially when it comes to tracking things like cross-platform changes. Might it be sufficient to just lock the branch and not delete it completely? Deleting a branch from Git after it has been pushed publicly might present certain issues (though removing a commit definitely does). It starts to head off into areas similar to using the 'obliterate' command in Perforce (hint: that one should be an extreme exception to common practice). I seem to recall that a pre or post commit hook might do the job of preventing further changes. -- Jon A. Cruz - Senior Open Source Developer Samsung Open Source Group jonc at osg.samsung.com _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
