On Thu, Jun 10, 2010 at 5:51 PM, Adam <[email protected]> wrote: > OK, thanks. That hurts, but I'll deal with it. > > Does Mercurial have the same sort of problems? I might switch to it > if not. >
Mercurial definitely doesn't have this problem at all; it's a distributed system. With Subversion, there's only one "true" repository, and so the notion of replicating to a 'slave' repository is ponderous, and fragile. If the slave repository falls out of sync, you're out of luck. With distributed systems, the entire core design revolves around multiple peer repositories replicating changesets back and forth with each other. ;-) But to be fair: the main reason this happened is because the way we've deployed the wiki. For Subversion, we have only one repository containing both code and wiki. For Mercurial, we've created multiple repositories per project: one for code, one for wiki, plus any more you want to create for branches. If we had set up Subversion to have a separate wiki repository, then this mistake never would have happened to you in the first place. -- 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.
