aboutsummaryrefslogtreecommitdiff
path: root/Command/ResolveMerge.hs
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-11-15 21:29:54 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-11-15 21:29:54 -0400
commit381766efcdddb4c8706408a90c515470a6aa43a7 (patch)
treedda693b36724839ff2daff0e0766b7bdd883ea2c /Command/ResolveMerge.hs
parent27fafd61c39f8436e19e8fd449b5851ead10bbd1 (diff)
Avoid backtraces on expected failures when built with ghc 8; only use backtraces for unexpected errors.
ghc 8 added backtraces on uncaught errors. This is great, but git-annex was using error in many places for a error message targeted at the user, in some known problem case. A backtrace only confuses such a message, so omit it. Notably, commands like git annex drop that failed due to eg, numcopies, used to use error, so had a backtrace. This commit was sponsored by Ethan Aubin.
Diffstat (limited to 'Command/ResolveMerge.hs')
-rw-r--r--Command/ResolveMerge.hs6
1 files changed, 3 insertions, 3 deletions
diff --git a/Command/ResolveMerge.hs b/Command/ResolveMerge.hs
index 8742a1104..0ba6efb36 100644
--- a/Command/ResolveMerge.hs
+++ b/Command/ResolveMerge.hs
@@ -33,8 +33,8 @@ start = do
( do
void $ commitResolvedMerge Git.Branch.ManualCommit
next $ next $ return True
- , error "Merge conflict could not be automatically resolved."
+ , giveup "Merge conflict could not be automatically resolved."
)
where
- nobranch = error "No branch is currently checked out."
- nomergehead = error "No SHA found in .git/merge_head"
+ nobranch = giveup "No branch is currently checked out."
+ nomergehead = giveup "No SHA found in .git/merge_head"