Petr Rockai wrote:
Recently, it has been noted, that for old-fashioned repositories, darcs
whatsnew has regressed in performance by a fair amount. This is true, but it's
not clear if it is worth addressing properly. For 2.3.1, the easy fix is to
restore the old code path when the repository is not hashed. However, I have
already removed unsafeDiff in darcs-hs and I want to keep it that way, so we
either need to start treating old-fashioned as second-class, or either come up
with a more systematic fix.
At this point the docs strongly suggest using hashed and/or darcs-2
formats and there are more reasons to push people away from
old-fashioned repositories beyond the performance work. Considering the
number of versions between the last 1.x release and the number of
distros that now have one 2.x release or another, perhaps it is time to
altogether officially deprecate old-fashioned repositories?
My suggestions for an upcoming release:
darcs init --old-fashioned # fails with a polite error message
darcs get --old-fashioned # has a yes/no warning, encouraging hashed
It may even be useful to add simple deprecation warnings to darcs pull
and darcs push along the lines of "Warning: the remote repository is in
an older inventory format that has been deprecated. Converting it to the
newer hashed-inventory format or darcs-2 format might result in
performance gains. More details can be found at website-uri."
To be honest, at this point I'm almost surprised that darcs 2.2.0 still
allows you to create old fashioned repositories.
--
--Max Battcher--
http://worldmaker.net
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
