Mercurial > hg-stable
changeset 19967:e92c6524a76d stable
largefiles: use 'remote'/'local' in merge prompts like in other merge prompts
Prompts like
foo has been turned into a largefile
use (l)argefile or keep as (n)ormal file?
was not as clear as the usual prompts that use 'remote' or 'local' to explain
what happened on which side ... especially not when used to the normal prompts.
"as" could also indicate that it would be possible to take the content of the
largefile and somehow put it into the normal file. It could make it more clear
that it was a choice between one side or the other.
For consistency we will now phrase it like:
remote turned local normal file f into a largefile
use (l)argefile or keep (n)ormal file?
author | Mads Kiilerich <madski@unity3d.com> |
---|---|
date | Mon, 28 Oct 2013 22:34:07 +0100 |
parents | 7985e3469f58 |
children | 7bec3f697d76 |
files | hgext/largefiles/overrides.py tests/test-issue3084.t |
diffstat | 2 files changed, 24 insertions(+), 24 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/largefiles/overrides.py Mon Oct 28 22:34:05 2013 +0100 +++ b/hgext/largefiles/overrides.py Mon Oct 28 22:34:07 2013 +0100 @@ -387,8 +387,8 @@ # the second parent lfile = splitstandin standin = f - msg = _('%s has been turned into a largefile\n' - 'use (l)argefile or keep as (n)ormal file?' + msg = _('remote turned local normal file %s into a largefile\n' + 'use (l)argefile or keep (n)ormal file?' '$$ &Largefile $$ &Normal file') % lfile if repo.ui.promptchoice(msg, 0) == 0: processed.append((lfile, "r", None, msg)) @@ -401,8 +401,8 @@ # the second parent standin = lfutil.standin(f) lfile = f - msg = _('%s has been turned into a normal file\n' - 'keep as (l)argefile or use (n)ormal file?' + msg = _('remote turned local largefile %s into a normal file\n' + 'keep (l)argefile or use (n)ormal file?' '$$ &Largefile $$ &Normal file') % lfile if repo.ui.promptchoice(msg, 0) == 0: processed.append((lfile, "r", None, msg))
--- a/tests/test-issue3084.t Mon Oct 28 22:34:05 2013 +0100 +++ b/tests/test-issue3084.t Mon Oct 28 22:34:07 2013 +0100 @@ -28,8 +28,8 @@ Normal file in the working copy, keeping the normal version: $ echo "n" | hg merge --config ui.interactive=Yes - foo has been turned into a largefile - use (l)argefile or keep as (n)ormal file? 0 files updated, 0 files merged, 1 files removed, 0 files unresolved + remote turned local normal file foo into a largefile + use (l)argefile or keep (n)ormal file? 0 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles 0 largefiles updated, 0 removed @@ -42,8 +42,8 @@ $ hg update -q -C $ echo "l" | hg merge --config ui.interactive=Yes - foo has been turned into a largefile - use (l)argefile or keep as (n)ormal file? 1 files updated, 0 files merged, 1 files removed, 0 files unresolved + remote turned local normal file foo into a largefile + use (l)argefile or keep (n)ormal file? 1 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles 1 largefiles updated, 0 removed @@ -70,8 +70,8 @@ $ hg update -q -C -r 1 $ echo "n" | hg merge --config ui.interactive=Yes - foo has been turned into a normal file - keep as (l)argefile or use (n)ormal file? 1 files updated, 0 files merged, 1 files removed, 0 files unresolved + remote turned local largefile foo into a normal file + keep (l)argefile or use (n)ormal file? 1 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles 0 largefiles updated, 0 removed @@ -98,8 +98,8 @@ $ hg update -q -C -r 1 $ echo "l" | hg merge --config ui.interactive=Yes - foo has been turned into a normal file - keep as (l)argefile or use (n)ormal file? 0 files updated, 0 files merged, 1 files removed, 0 files unresolved + remote turned local largefile foo into a normal file + keep (l)argefile or use (n)ormal file? 0 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles 1 largefiles updated, 0 removed @@ -219,8 +219,8 @@ $ hg merge -r large local changed f which remote deleted use (c)hanged version or (d)elete? c - f has been turned into a largefile - use (l)argefile or keep as (n)ormal file? l + remote turned local normal file f into a largefile + use (l)argefile or keep (n)ormal file? l 1 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles @@ -231,8 +231,8 @@ $ hg up -Cqr normal2 $ ( echo c; echo n ) | hg merge -r large --config ui.interactive=Yes local changed f which remote deleted - use (c)hanged version or (d)elete? f has been turned into a largefile - use (l)argefile or keep as (n)ormal file? 0 files updated, 0 files merged, 1 files removed, 0 files unresolved + use (c)hanged version or (d)elete? remote turned local normal file f into a largefile + use (l)argefile or keep (n)ormal file? 0 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles 0 largefiles updated, 0 removed @@ -255,8 +255,8 @@ $ hg merge -r normal2 remote changed f which local deleted use (c)hanged version or leave (d)eleted? c - f has been turned into a normal file - keep as (l)argefile or use (n)ormal file? l + remote turned local largefile f into a normal file + keep (l)argefile or use (n)ormal file? l 1 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles @@ -267,8 +267,8 @@ $ hg up -Cqr large $ ( echo c; echo n ) | hg merge -r normal2 --config ui.interactive=Yes remote changed f which local deleted - use (c)hanged version or leave (d)eleted? f has been turned into a normal file - keep as (l)argefile or use (n)ormal file? 2 files updated, 0 files merged, 1 files removed, 0 files unresolved + use (c)hanged version or leave (d)eleted? remote turned local largefile f into a normal file + keep (l)argefile or use (n)ormal file? 2 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles 0 largefiles updated, 0 removed @@ -312,8 +312,8 @@ $ hg merge -r normal local changed .hglf/f which remote deleted use (c)hanged version or (d)elete? c - f has been turned into a normal file - keep as (l)argefile or use (n)ormal file? l + remote turned local largefile f into a normal file + keep (l)argefile or use (n)ormal file? l 0 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles @@ -337,8 +337,8 @@ $ hg merge -r large2 remote changed .hglf/f which local deleted use (c)hanged version or leave (d)eleted? c - f has been turned into a largefile - use (l)argefile or keep as (n)ormal file? l + remote turned local normal file f into a largefile + use (l)argefile or keep (n)ormal file? l 2 files updated, 0 files merged, 1 files removed, 0 files unresolved (branch merge, don't forget to commit) getting changed largefiles