The git UI can be improved by addressing the error messages to those they help: inexperienced and casual git users. To this intent, it is helpful to make sure the terms used in those messages can be understood by this segment of users, and that they guide them to resolve the problem.
In particular, failure to apply a patch during a git rebase is a common problem that can be very destabilizing for the inexperienced user. It is important to lead them toward the resolution of the conflict (which is a 3-steps process, thus complex) and reassure them that they can escape a situation they can't handle with "--abort". This commit answer those two points by detailling the resolution process and by avoiding cryptic git linguo. Signed-off-by: William Duclot <william.duc...@gmail.com> --- While I do not expect that this V1 wording will be to the liking of everyone, I think (know?) that the heart of this patch isn't something that I'm the only one bothered with :) I'd very much like to hear your opinions about it git-rebase.sh | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/git-rebase.sh b/git-rebase.sh index 2cf73b88e..50457f687 100755 --- a/git-rebase.sh +++ b/git-rebase.sh @@ -55,9 +55,10 @@ LF=' ' ok_to_skip_pre_rebase= resolvemsg=" -$(gettext 'When you have resolved this problem, run "git rebase --continue". -If you prefer to skip this patch, run "git rebase --skip" instead. -To check out the original branch and stop rebasing, run "git rebase --abort".') +$(gettext 'Resolve this conflict manually, mark it as resolved with "git add <conflicted_file>", +then run "git rebase --continue". +You can instead skip this commit: run "git rebase --skip". +To stop the whole rebasing and get back to your pre-rebase state, run "git rebase --abort".') " unset onto unset restrict_revision -- 2.13.0
