Changing the v1 repo to another name(directory rename) is simple enough. 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.
I would hate for something like that to happen to a repo a project uses to build server software. ----- Rom -----Original Message----- From: Oliver Bock [mailto:[email protected]] Sent: Friday, March 22, 2013 6:11 AM To: Rom Walton Cc: BOINC Dev Mailing List; [email protected] Subject: Re: [boinc_dev] [boinc_projects] BOINC Git Migration v2 On 3/22/13 9:37 , Oliver Bock wrote: >> Once Oliver has completed updating the boinc-v2.git repo, all future >> BOINC development work will happen out of that repo. > > How about renaming boinc.git to boinc-v1.git (for the archive) and use > boinc.git for v2? boinc-v2.git is kinda awkward. When I'm done that is. If you need help doing that, let me know. You could basically remove/empty the existing repos and let me push them again to their new respective homes... 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.
