summaryrefslogtreecommitdiff
path: root/builtin/am.c
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2017-06-04 10:20:58 +0900
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-06-04 10:20:59 +0900
commit0501b7e78564d11e87d228f7ffdbdb4b147145e3 (patch)
treedd388bb6e4b8ca0bb876fe0ceec01379d492d0fc /builtin/am.c
parentMerge branch 'bw/submodule-with-bs-path' into maint (diff)
parentgit-filter-branch: be more direct in an error message (diff)
downloadtgif-0501b7e78564d11e87d228f7ffdbdb4b147145e3.tar.xz
Merge branch 'ja/do-not-ask-needless-questions' into maint
Git sometimes gives an advice in a rhetorical question that does not require an answer, which can confuse new users and non native speakers. Attempt to rephrase them. * ja/do-not-ask-needless-questions: git-filter-branch: be more direct in an error message read-tree -m: make error message for merging 0 trees less smart aleck usability: don't ask questions if no reply is required
Diffstat (limited to 'builtin/am.c')
-rw-r--r--builtin/am.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/builtin/am.c b/builtin/am.c
index a95dd8b4e6..dd60fad1e6 100644
--- a/builtin/am.c
+++ b/builtin/am.c
@@ -1312,7 +1312,7 @@ static int parse_mail(struct am_state *state, const char *mail)
}
if (is_empty_file(am_path(state, "patch"))) {
- printf_ln(_("Patch is empty. Was it split wrong?"));
+ printf_ln(_("Patch is empty."));
die_user_resolve(state);
}
@@ -1940,7 +1940,8 @@ static void am_resolve(struct am_state *state)
if (unmerged_cache()) {
printf_ln(_("You still have unmerged paths in your index.\n"
- "Did you forget to use 'git add'?"));
+ "You should 'git add' each file with resolved conflicts to mark them as such.\n"
+ "You might run `git rm` on a file to accept \"deleted by them\" for it."));
die_user_resolve(state);
}