Ticket #186 (closed defect: fixed)
mercurial checkouts should separate clone and update
|Reported by:||dsallings||Owned by:|
|Cc:||dustin, bhearsum, Pike, afri, even, marcusl|
The current vc full model uses clone -r to get a tree to a particular version. This is incorrect in the case where the target version is in a named branch. The repository history will be truncated at the correct location, but the automatic checkout will be on the default branch (as of 0.9.5).
The ideal behavior is to clone *without* a checkout, and then update to the correct revision after the clone.
The attached patch is how we're doing this. You could possibly do both (clone without checkout to a revision and then update to that revision), but I think that the difference will generally be negligible.
comment:15 Changed 4 years ago by dustin
- Keywords mercurial added; mercurial, review removed
- Status changed from new to closed
- Resolution set to fixed