On 3/22/13 18:23 , Rom Walton wrote: > I would hesitate about change the v2 repo to boinc.git. IIRC, Eric K. > had started using one out our pre-v1 repos and when we completed the > final migration and went public he had merge issues when he went to pull > from the new repo.
Well, that's to be expected. Everyone has to clone the new repo to work with it and all custom branches people might already have started locally need to be cherry-picked over to the new repo. This is something we can't change and that's why it is so important to get this migration right. I myself will have to spend a number of days re-attaching all of our E@H custom branches. Anyhow, I still think renaming v2 to simply boinc.git is worthwhile since this is going to be the final name you're going to use for the next couple of years. The earlier you change the name, the less users will be affected by the change. > I would hate for something like that to happen to a repo a project uses > to build server software. This should just be a matter of communication. People need to be made aware of the new repo and that they can't simply pull from or push to it. Something we already started with this very email. But you should post some more prominent news about this fact, in particular directly addressing those with push access. If you're afraid that people with push access might mess up the central repo, revoke their push access privileges (and inform them!) until they confirmed they made the switch to the new repo. Cheers, Oliver _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
