Re: [crossfire] Git for arch, maps, server, and client
On 5/5/21 10:44 AM, Kevin Zheng wrote: On 5/5/21 9:30 AM, Mark Wedel wrote: It looks like write (commit) access can be removed from the SVN repos in sourceforge while still letting them exist. I'd suggest that be done, just to prevent any accidental commits (someone forgot to update their paths or whatever else). Plus, it can be used to make sure no one commits anything while you are moving things over. Thanks for the suggestion. This wasn't going to be so easy, because there were other subfolders in the repository that weren't part of this migration. Looking at the repo now, however, the only sub-directories left are jxclient, metaserver, and sounds. If we also go ahead and migrate these over too, we can go ahead and make the entire SVN read-only after the switch. If there are no objections, I will also go ahead and migrate jxclient, metaserver, and sounds. I think that is a good idea - it makes more sense to me that everything under the project is using the same source code control system, vs some using git and others using SVN. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Git for arch, maps, server, and client
On 5/5/21 9:30 AM, Mark Wedel wrote: It looks like write (commit) access can be removed from the SVN repos in sourceforge while still letting them exist. I'd suggest that be done, just to prevent any accidental commits (someone forgot to update their paths or whatever else). Plus, it can be used to make sure no one commits anything while you are moving things over. Thanks for the suggestion. This wasn't going to be so easy, because there were other subfolders in the repository that weren't part of this migration. Looking at the repo now, however, the only sub-directories left are jxclient, metaserver, and sounds. If we also go ahead and migrate these over too, we can go ahead and make the entire SVN read-only after the switch. If there are no objections, I will also go ahead and migrate jxclient, metaserver, and sounds. Regards, Kevin ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
Re: [crossfire] Git for arch, maps, server, and client
On 5/4/21 11:45 PM, Kevin Zheng wrote: Hi there, Some months ago I proposed switching the arch, maps, server, and client repositories to Git. Since feedback on the mailing list was positive, I think now is a good time to make the switch. - At UTC Saturday 2021-05-08 22:00, I will update these Git repositories from SVN one last time. Future commits in these repositories should go into Git. SVN will continue to be used for the repositories that haven't switched. The migrated repositories will still continue to exist in SVN for a while, but should not be committed to. Hopefully nobody gets confused by the fact that there are two repositories. At some point, perhaps we should delete these repositories from SVN. It looks like write (commit) access can be removed from the SVN repos in sourceforge while still letting them exist. I'd suggest that be done, just to prevent any accidental commits (someone forgot to update their paths or whatever else). Plus, it can be used to make sure no one commits anything while you are moving things over. Thanks for doing this work. ___ crossfire mailing list crossfire@metalforge.org http://mailman.metalforge.org/mailman/listinfo/crossfire
