sapling/tests/test-push-hook-lock.out

adding foo
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
pushing to ../2
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
Create local ui object per repository, so .hg/hgrc don't get mixed. This is needed for hooks, but may be important for other settings, too. Fixes issue113, also integrated push-hook-lock.sh as a test case for this. 2006-03-06 19:47:41 +03:00			`adding foo`
Make hg update more verbose by default (issue12) (including small changes to revert and backout to not show these stats with the exception of backout --merge) Show update stats (unless -q), e.g.: K files updated, L files merged, M files removed, N files unresolved Inform the user what to do after a merge: (branch merge, don't forget to commit) Inform the user what to do if a branch merge failed: There are unresolved merges, you can redo the full merge using: hg update -C X hg merge Y Inform the user what to do if a working directory merge failed: There are unresolved merges with locally modified files. 2006-05-02 20:44:02 +04:00			`1 files updated, 0 files merged, 0 files removed, 0 files unresolved`
			`1 files updated, 0 files merged, 0 files removed, 0 files unresolved`
Create local ui object per repository, so .hg/hgrc don't get mixed. This is needed for hooks, but may be important for other settings, too. Fixes issue113, also integrated push-hook-lock.sh as a test case for this. 2006-03-06 19:47:41 +03:00			`pushing to ../2`
			`searching for changes`
			`adding changesets`
			`adding manifests`
			`adding file changes`
			`added 1 changesets with 1 changes to 1 files`