I got this *after* spending an hour downloading patches.  Is it stupid
to offer to create a lazy repository at this point?

$ ssh soy darcs get --complete --tag 2.1.0pre3 http://darcs.net/
[...]
Copying patches 6278/6280
Writing inventory 5/49
Writing inventory 19/49
Welcome to the darcs stable repository.
**********************
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 5 patches.
Finished getting.

Thanks a lot. Just to clarify: You would like the offer to create a lazy 
repository to appear at a much earlier point in time. Please correct me if this 
is wrong.

Best regards
Thorkil

On Tue, Oct 28, 2008 at 11:22:57AM -0000, Thorkil Naur wrote:
> Thanks a lot. Just to clarify: You would like the offer to create a
> lazy repository to appear at a much earlier point in time. Please
> correct me if this is wrong.

Really, I think if I have explicitly asked for --complete, it should
not offer to create a lazy repository at all.

AIUI the current behaviour is clearly wrong, because with --complete
it offers to create a lazy repository after that's no longer possible
(because the potentially "lazy" parts have already been downloaded).

On Tuesday 28 October 2008 13:35, Trent Buck wrote:
> ...
> Really, I think if I have explicitly asked for --complete, it should
> not offer to create a lazy repository at all.
> 
> AIUI the current behaviour is clearly wrong, because with --complete
> it offers to create a lazy repository after that's no longer possible
> (because the potentially "lazy" parts have already been downloaded).

Thanks a lot, my mistake.

Best regards
Thorkil

I am leaving this with wishlist priority, since I presume that it doesn't really 
prevent any particular use of darcs. So now we only need a volunteer to do the 
real work.

Thanks and best regards
Thorkil

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

* resolve issue1122: get --complete should not offer to create a lazy repository 
Ignore-this: da8a1d30869e6153c027ae396cc74d56