mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 00:45:18 +03:00
0cb0a7ba67
The recently introduced message was: no unresolved files; you may continue your unfinished operation This had three problems: - looks a bit like an error message because it's not saying "we've just resolved the last file" - refers to "unfinished operation", which won't be the case with "update" or "merge" - introduces semicolons to error messages, which is stylistically questionable I've simplified this to: no more unresolved files In the future, if we want to prompt someone to continue a particular operation, we should use a hint style: no more unresolved files (use 'hg graft --continue' to finish grafting)
48 lines
1021 B
Perl
48 lines
1021 B
Perl
$ addcommit () {
|
|
> echo $1 > $1
|
|
> hg add $1
|
|
> hg commit -d "${2} 0" -m $1
|
|
> }
|
|
|
|
$ commit () {
|
|
> hg commit -d "${2} 0" -m $1
|
|
> }
|
|
|
|
$ hg init a
|
|
$ cd a
|
|
$ addcommit "A" 0
|
|
$ addcommit "B" 1
|
|
$ echo "C" >> A
|
|
$ commit "C" 2
|
|
|
|
$ hg update -C 0
|
|
1 files updated, 0 files merged, 1 files removed, 0 files unresolved
|
|
$ echo "D" >> A
|
|
$ commit "D" 3
|
|
created new head
|
|
|
|
Merging a conflict araises
|
|
|
|
$ hg merge
|
|
merging A
|
|
warning: conflicts during merge.
|
|
merging A incomplete! (edit conflicts, then use 'hg resolve --mark')
|
|
1 files updated, 0 files merged, 0 files removed, 1 files unresolved
|
|
use 'hg resolve' to retry unresolved file merges or 'hg update -C .' to abandon
|
|
[1]
|
|
|
|
Correct the conflict without marking the file as resolved
|
|
|
|
$ echo "ABCD" > A
|
|
$ hg commit -m "Merged"
|
|
abort: unresolved merge conflicts (see hg help resolve)
|
|
[255]
|
|
|
|
Mark the conflict as resolved and commit
|
|
|
|
$ hg resolve -m A
|
|
no more unresolved files
|
|
$ hg commit -m "Merged"
|
|
|
|
$ cd ..
|