Previously we allowed a sync commit to happen at any time, but imported the
full repository to bring it into sync. This is slow for very large repositories
and might be accidentally triggered. We change this behavior to only do a sync
commit if only the imported client changed but nothing else.
Details
- Reviewers
kaleyh
cd tests python ../../hg-crew/tests/run-tests.py test-p4fastimport-*.t test-check*.t
Diff Detail
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
tests/test-p4fastimport-blobcommit.t | ||
---|---|---|
134 | What client will it use if we fall back to fast import ? Since CL 5 touches files that are not in the current client spec, will fast import be able to update the repo to CL5? |
tests/test-p4fastimport-blobcommit.t | ||
---|---|---|
134 | Yes, using the old clientspec it will be able to update it. |
tests/test-p4fastimport-blobcommit.t | ||
---|---|---|
134 | In case p4fastimport uses the new client-spec, it behaves like before: if a file changes it will happily included it. So what we want to do is: use the new-spec only after p4syncimport changed. Maybe in an upcoming change we can save information about the clientspec in Mercurial to automatically detect a change in the p4fastimport case |
tests/test-p4fastimport-blobcommit.t | ||
---|---|---|
134 | that can be a good idea |
What client will it use if we fall back to fast import ? Since CL 5 touches files that are not in the current client spec, will fast import be able to update the repo to CL5?