[darcs-devel] [issue2123] provide feedback when fetching missing --lazy files

[Eric Kow]

Eric Kow <kowey at darcs.net> added the comment:

I think this is a more general feature request, one that stretches beyond 
darcs check.

Basically, when you're doing something like a darcs get or a darcs pull, 
you *expect* to grab files from the fetched repo.  But there are some 
situations where you won't be expecting such a thing to happen:

- operations that are not specifically about retrieval (so not pull/get)
- fetching from repositories other than the one you asked for (--lazy 
chaining: darcs get --lazy X Y; darcs get Y Z; cd Z; darcs pull)

In cases where it is not immediately obvious that Darcs should want to 
fetch files from some remote source, we should announce that we are doing 
so.

We don't need to mention this for each file that we fetch.  It's enough 
to mention the location once:

Fetching some missing patches from location X

Note also that we don't necessarily have to make the distinction between 
expecting fetching and not-expected.  Maybe the same UI could be used to 
report that we're fetching files from the places we'd expect (which could 
be reassuring)

I think here we have a UI design sketched out (?), but we now need 
somebody to figure out the code-design and hopefully implement it

----------
priority:  -> feature
status: unknown -> need-design
title: darcs check on a lazy repository begins pulling patches over the network without informing the user -> provide feedback when fetching missing --lazy files
topic: +Hashed

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue2123>
__________________________________