Mercurial and git solve all replica problems, and some more.

They are infinitely faster, more reliable, and more useful. And in
some ways they are even conceptually simpler (I never quite understood
some of the most subtle points of replica, like why it keeps saying it
needs to update files that were already updated if I happen to have
some local changes elsewhere, even when I have had them explained to
me repeatedly, of course that is due to my own intellectual
limitations, but...)

The git codebase is considerably more complex, but that is because it
does tons of things we don't really need to replace replica, I even
got a port of git almost going. If it is agreed to replace replica
with git, I will be happy to work on porting the latest git version.
(It already works under linuxemu).

Mercurial is much simpler (at some point it was about seven thousand
lines of python, it has grown since, but the useful stuff was all
already there), and it think some people got it to work with their
various python ports (not sure which, there are so many that I lost
track), and mjl has a very nice read only limbo implementation, and
said making it write wouldn't be too hard (the tricky stuff is merges
and such, which we don't really need to replace replica).

So, all that is needed to get rid of replica is the determination to
do so, and I'm sure many people will be happy to help in the effort.

Peace

uriel

P.S.: Other problems this would solve is fast and efficient mirroring,
web interfaces to the source and history, etc.

On Wed, Jan 28, 2009 at 12:32 AM, Russ Cox <r...@swtch.com> wrote:
>> But people keep telling me that replica's unreliability, painful
>> slowness, and general clunkyness,  are all in my imagination, so what
>> do I know...
>
> No, what we've told you, repeatedly, is that
> whining about problems and fixing them are
> two different things.  Fixes are appreciated.
>
> Russ
>
>

Reply via email to