mirror of
https://github.com/facebook/sapling.git
synced 2024-10-07 23:38:50 +03:00
153675561e
With this change, "hg clone" looks like this: % hg clone http://example.com/repo/big big requesting all changes adding changesets adding manifests adding file changes added XXX changesets with XXX changes to XXX files updating working directory XXX files updated, XXX files merged, XXX files removed, XXX files unresolved So the user sees % hg clone http://example.com/repo/big big requesting all changes adding changesets adding manifests adding file changes added XXX changesets with XXX changes to XXX files updating working directory while Mercurial is writing to disk to populate the working directory With this change, "hg clone" looks like this: % hg clone big big-work updating working directory XXX files updated, XXX files merged, XXX files removed, XXX files unresolved
16 lines
521 B
Plaintext
16 lines
521 B
Plaintext
% init foo-base
|
|
% create alpha in first repo
|
|
adding alpha
|
|
% clone foo-base to foo-work
|
|
updating working directory
|
|
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
% create beta in second repo
|
|
adding beta
|
|
% create gamma in first repo
|
|
adding gamma
|
|
% pull into work and merge
|
|
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
(branch merge, don't forget to commit)
|
|
% revert to changeset 1 to simulate a failed merge
|
|
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
|