sapling/tests/test-patch.out

adding a
% check custom patch options are honored
requesting all changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
updating working directory
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
applying ../a.diff
Using custom patch
nothing changed
Add tests for ui.patch regression. 2007-06-21 01:32:31 +04:00			`adding a`
			`% check custom patch options are honored`
			`requesting all changes`
			`adding changesets`
			`adding manifests`
			`adding file changes`
			`added 1 changesets with 1 changes to 1 files`
clone: print "updating working directory" status message 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 2008-03-21 16:52:24 +03:00			`updating working directory`
Add tests for ui.patch regression. 2007-06-21 01:32:31 +04:00			`1 files updated, 0 files merged, 0 files removed, 0 files unresolved`
			`applying ../a.diff`
			`Using custom patch`
			`nothing changed`