Message ID | pull.934.git.1618770806366.gitgitgadget@gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | git-merge: move space to between strings | expand |
"Josh Soref via GitGitGadget" <gitgitgadget@gmail.com> writes: > From: Josh Soref <jsoref@gmail.com> > > Signed-off-by: Josh Soref <jsoref@gmail.com> > --- > git-merge: move space to between strings > > GitHub Actions show things like: > > * branch master -> FETCH_HEAD > (nothing to squash)Already up to date. > > > The expected results are: > > * branch master -> FETCH_HEAD > (nothing to squash) Already up to date. I am not sure if that is THE expected results, though (you wouldn't have got this reaction if you said "I would expect to see"). Usually, it is easier to read a message if it makes its primary point first, before giving a parenthetical note. I.e. I would expect that Already up to date (nothing to squash). would be easier to understand to users. Thanks.
diff --git a/builtin/merge.c b/builtin/merge.c index 062e91144125..0d8c782cccb2 100644 --- a/builtin/merge.c +++ b/builtin/merge.c @@ -383,7 +383,7 @@ static void restore_state(const struct object_id *head, static void finish_up_to_date(const char *msg) { if (verbosity >= 0) - printf("%s%s\n", squash ? _(" (nothing to squash)") : "", msg); + printf("%s%s\n", squash ? _("(nothing to squash) ") : "", msg); remove_merge_branch_state(the_repository); }