I think there's confusion here. Let me try to clear up some facts. :-) Subversion is a stand-alone product; it's got a huge developer and user community, it's own project site. There are dozens of books about it and dozens of discussion groups for getting support.
Google is just a hosting site, just like Sourceforge or Berlios or a dozen other places. None of these hosting sites are "the place" to get specific tech support for Subversion: they just provide servers. (Unless, of course, your problem is tickling some specific bug in the hoster's subversion servers -- but it's pretty clear that's not the case here. You simply did a whole bunch of complex merging and the svn core product got confused and messed things up for you.) In that same vein, it's out-of-scope for Google (or any other hosting service) to start putting up public service announcements about the various bugs of Subversion or Mercurial -- at a minimum, it would be redundant. The internet is *full* of public discussions and blog posts about how Subversion's merge-tracking is very brittle; even the official Subversion Book goes into great deal about its limitations, how to be careful, etc. Maybe Google could've pointed this out when we announced our upgrade to 1.5 and 1.6, but at most, I think any wiki docs we have should be pointing at public support resources -- not setting expectations that we are a source of individual troubleshooting for indivduals. It seems odd that Stephen Kung would have pointed you to Google for help, rather than any of subversion's main user-support forums. That's a bit like asking Apple for help when some 3rd-party iPhone app doesn't work as it should. :-) Sorry to mislead on the wiki page -- the only reason we recommend svn for smaller projects is because it's good 'first version control system' for projects with 1 or 2 people. It's slightly easier to learn. But svn and mercurial can both handle any size project. What I was simply recommending was to toss your history -- just start over a with a 'clean' tree of code (presumably something you assemble carefully by cherrypicking various patches from different branches). Then import that code to mercurial. If you look at your project's Admin tab, you can flip your project to mercurial at any time (you just start with an empty repository.) Before giving up and abandoning history and switching to a new system, though, try to get the merge-tracking experts on us...@subversion.tigris.org to analyze your situation. I've seen them untangle some big messes. If you *do* decide to switch to mercurial, please skim the free online book! Play around with it a bit on some scratch data to get a feel for it first! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to google-code-hosting@googlegroups.com To unsubscribe from this group, send email to google-code-hosting+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
