error_resolve_conflict: rewrap advice message
authorJeff King <peff@peff.net>
Tue, 3 Jun 2014 07:17:17 +0000 (03:17 -0400)
committerJunio C Hamano <gitster@pobox.com>
Tue, 3 Jun 2014 17:04:19 +0000 (10:04 -0700)
If you try to commit with unresolved conflicts in the index,
you get this message:

$ git commit
U foo
error: 'commit' is not possible because you have unmerged files.
hint: Fix them up in the work tree,
hint: and then use 'git add/rm <file>' as
hint: appropriate to mark resolution and make a commit,
hint: or use 'git commit -a'.
fatal: Exiting because of an unresolved conflict.

The irregular line-wrapping makes this awkward to read, and
it takes up more lines than necessary. Instead, let's rewrap
it to about 60 characters per line:

$ git commit
U foo
error: 'commit' is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit, or use
hint: 'git commit -a'.
fatal: Exiting because of an unresolved conflict.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
advice.c
index 3eca9f5ffdd6e3596584ed0aa79e2634683bd496..d458ae77481128680f0cc67aae6845d16ea548d4 100644 (file)
--- a/advice.c
+++ b/advice.c
@@ -84,10 +84,9 @@ int error_resolve_conflict(const char *me)
                 * Message used both when 'git commit' fails and when
                 * other commands doing a merge do.
                 */
-               advise(_("Fix them up in the work tree,\n"
-                        "and then use 'git add/rm <file>' as\n"
-                        "appropriate to mark resolution and make a commit,\n"
-                        "or use 'git commit -a'."));
+               advise(_("Fix them up in the work tree, and then use 'git add/rm <file>'\n"
+                        "as appropriate to mark resolution and make a commit, or use\n"
+                        "'git commit -a'."));
        return -1;
 }