Maybe it would be good to always create hashed repos, even if we're fetching
from traditional repos.  This might be slower if we have compute the hashes, and
it might not encourage people to start using hashed repos on their server... but
on the other hand if we do this, then people get things like Unison-proofing and
case-insensitivity robustness.  They just don't benefit as much from things like
the global cache, or the lazy gets.

+1.  I actually thought this was the default already; clearly it's just my
~/.darcs/defaults doing it for me!

When should we target this for?  Darcs 2.3, or right now?

I think we want to change a whole bunch of default settings (e.g. making --dont-allow-conflicts
the default).  Should we address all of these at once, with a meged BTS ticket / wiki blueprint
page?

On Sat, Apr 18, 2009 at 03:42:51 -0000, Trent Buck wrote:
> I think we want to change a whole bunch of default settings (e.g.
> making --dont-allow-conflicts the default).  Should we address all of
> these at once, with a meged BTS ticket / wiki blueprint page?

I think you're thinking of
  http://wiki.darcs.net/index.html/DefaultSwitches

We should prioritise this.
See http://bugs.darcs.net/issue1453

The following patch updated the status of issue1435 to be resolved:

* Resolve issue1435: default to get --hashed from a darcs-1.0 source. 
Ignore-this: 99a81c9ccc4da84a76ea6323c2d8c51e