On Thursday 21 August 2008, Max Battcher wrote: > I recommend using darcs-2 format for new projects and I think that > there are also good opportunities (such as just after a big release) > for existing projects to move to darcs-2 format. At the very least, > new projects shouldn't have to put up with old sorts of conflict > failures that darcs-2 format should eliminate.
While you praise all the new goodies in darcs2, you should also mention that it has bugs that prevent it from working (I'm not referring here to performance issues). See for example issue966: http://bugs.darcs.net/issue966 That bug makes darcs diff unusable as soon as you record a tag, which is exactly what happens on a release. darcsweb is also broken as a result of this and shows empty patches. People who seek to migrate to darcs2, should be aware of these issues before making a decision, because it's not only about better repository formats. IMO, such bugs that cripple or make darcs-2 unusable in certain situations should be higher on the priority list of fixes for the next release than performance enhancing fixes, especially if the aforementioned situations are pretty common. That is not to say that performance enhancing fixes are not important, only that I can live for a while with a less performant darcs, but I can't live with one that doesn't work. -- Dan _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
