According to the ConvertingSvnToHg wiki on GCPH support: "Your old Subversion project will still be accessible after you switch your project to using Mercurial, …"
I understood "accessible" to mean pretty much functional as far as source control goes. A few months back, I moved just the trunk of the ELMAH project (http://elmah.googlecode.com) over to Hg. Porting the entire history with full fidelity was proving to be difficult and not worth the overall effort. I figured that if the time came to make a quick fix to one of the older release branches then it could be just applied to the SVN repo and a service release issued. That time came and I learned the hard way that commits to the SVN repo were no longer possible. I was wondering if this can be enabled for my project. Is there any technical reason not to allow the non-default SVN repo to be fully functional, at least for the project owner? Thanks, Atif -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
