3 patches for repository http://darcs.net:

Sat Apr 17 03:56:44 MSD 2010  Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
  * Resolve issue1159: smart caches union.
  Try to do better than just blindly copying remote cache entries:
  
  * If remote repository is accessed through network, do not copy any cache
    entries from it. Taking local entries does not make sense and using network
    entries can lead to darcs hang when it tries to get to unaccessible host.
  
  * If remote repositoty is local, copy all network cache entries. For local
    cache entries if the cache directory exists and is writable it is added as
    writable cache, if it exists but is not writable it is added as read-only
    cache.
  
  This approach should save us from bogus cache entries. One case it does not
  work very well is when you fetch from partial repository over network.
  Hopefully this is not a common case.

Sun Apr 18 18:01:29 MSD 2010  Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
  * URL: add maxPipelineLength function, rename maxPipeLength to maxPipelineLengthRef.

Sun Apr 18 18:47:04 MSD 2010  Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
  * Darcs.Repository: use pipelining when copying patches.
  Speculate on patches in fetch_patches_if_necessary. Improves darcs get time
  fot the http://darcs.net repository from 37:24 to 21:25 for me.

Attachments

• resolve-issue1159_-smart-caches-union_.dpatch
• unnamed

Long description amended in patch215.

On Sun, Apr 18, 2010 at 15:08:08 +0000, Dmitry Kurochkin wrote:
> Long description amended in patch215.

One useful trick here is darcs send --subject '[patch214]'
darcs send/procmail/roundup cooperation :-)

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9