Warning: very drafty page.

About darcs get vs darcs put, or: - should we hide darcs put - should we remove darcs put - should we reimplement it

A few remarks on the necessity to have darcs put, and the get/put symmetry. The complementarity of these two commands is commonly described as “get is used to bring a remote repository to a local place, put is used to put a local repository to a remote place”. But the reason why put was added, instead of letting get clone repositories to distant locations, is not just this. Put is used to create clones that do not have information about the original repository. Hence put always creates complete repositories (while get can create lazy ones).

pull –all and push –all against empty repositories: can it be optimized?

This is related to the idea of a “darcs complete” command, that could turn any repository into a complete repository, possibily without any default remote repo.