Thanks for the suggestions everyone, but checkpoints don't seem to speed up this repository much (not sure why). I will keep it around as a periodic benchmark to see how much better things get with new darcs releases. There seems to be a lot of exciting work in improving darcs' efficiency, so I'll do what I can to test it.

It's easy to convince people darcs has the best model and is a very powerful yet easy to use version control system. However it's hard to convince people to use it when its so incredibly slow on an existing codebase. I've no doubt I could get them to switch from SVN at work if darcs can be made fast enough for common operations. Keep up the good work and I'm sure that'll eventually be the case.

  - Jim

Tomasz Zielonka wrote:
On Sun, May 15, 2005 at 02:26:42PM -0400, James Bruce wrote:
Is it really that case that *nobody* has run into the problem I described below?

I am not sure, but it may occur more often when you convert from other VCS, when you have unordered tags.

The way to deal with this with stable darcs is to pull a tag to a fresh
repository, checkpoint it, and the pull the rest of patches.

With darcs-unstalbe you could try this command:
    darcs optimize --checkpoint --reorder-patches-like

Since I wasn't able to provide a solution for the people at work in a timely manner, it looks like they'll be moving to Subversion. I still love darcs and use it for my personal projects, but I feel like we missed an opportunity.

That's a shame :-(

Best regards
Tomasz


_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users

Reply via email to