Cloning is expensive especially on large repositories. We could use a new function which will retrieve only the concerned revision:
| |
| priority | important |
|---|---|
| type | enhancement |
| appeared in | <not specified> |
| done in | 2.1.0 |
| load | 2.000 |
| load left | 2.000 |
| closed by | <not specified> |
Logilab.org 
[register] [login]
#19308 TestConfig name cannot have space inside
Comments
-
2010/01/20 11:48, written by sthenault
| reply to this comment
-
2010/02/07 19:46, written by pydavid
| reply to this comment
-
2010/09/23 13:50, written by sthenault
| reply to this comment
- not sure it's quick than cloning a local repo
- needs apycot change to control/get used revision
-
2010/09/23 14:01, written by pydavid
| reply to this comment
- It's only as fast if hardlinking are avaible. If the repository are on another partition than the apycot execution, cloning will be much slower
- hg archive contains a .hg_archival.txt file with the following data:
(add comment)the pb is that archive needs a local repository
We may cache all remote repositories in a dedicated space. It would fix the "local_repository relation issue" at the same time.