From: Andrew Wong <andrew.kw.w@gmail.com>
To: git@vger.kernel.org
Cc: Andrew Wong <andrew.kw.w@gmail.com>
Subject: [PATCH 1/3] wt-status: Make status messages more consistent with others
Date: Fri, 14 Mar 2014 00:37:50 -0400 [thread overview]
Message-ID: <1394771872-25940-2-git-send-email-andrew.kw.w@gmail.com> (raw)
In-Reply-To: <1394771872-25940-1-git-send-email-andrew.kw.w@gmail.com>
This is mainly changing messages that say:
run "git foo --bar"
to
use "git foo --bar" to baz
Although the commands and flags are usually self-explanatory, this is
more consistent with other status messages, and gives some sort of
explanation to the user.
Signed-off-by: Andrew Wong <andrew.kw.w@gmail.com>
---
wt-status.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/wt-status.c b/wt-status.c
index a452407..9f2358a 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -899,13 +899,13 @@ static void show_merge_in_progress(struct wt_status *s,
status_printf_ln(s, color, _("You have unmerged paths."));
if (s->hints)
status_printf_ln(s, color,
- _(" (fix conflicts and run \"git commit\")"));
+ _(" (fix conflicts and use \"git commit\" to conclude the merge)"));
} else {
status_printf_ln(s, color,
_("All conflicts fixed but you are still merging."));
if (s->hints)
status_printf_ln(s, color,
- _(" (use \"git commit\" to conclude merge)"));
+ _(" (use \"git commit\" to conclude the merge)"));
}
wt_status_print_trailer(s);
}
@@ -922,7 +922,7 @@ static void show_am_in_progress(struct wt_status *s,
if (s->hints) {
if (!state->am_empty_patch)
status_printf_ln(s, color,
- _(" (fix conflicts and then run \"git am --continue\")"));
+ _(" (fix conflicts and then use \"git am --continue\" to continue)"));
status_printf_ln(s, color,
_(" (use \"git am --skip\" to skip this patch)"));
status_printf_ln(s, color,
@@ -994,7 +994,7 @@ static void show_rebase_in_progress(struct wt_status *s,
_("You are currently rebasing."));
if (s->hints) {
status_printf_ln(s, color,
- _(" (fix conflicts and then run \"git rebase --continue\")"));
+ _(" (fix conflicts and then use \"git rebase --continue\" to continue)"));
status_printf_ln(s, color,
_(" (use \"git rebase --skip\" to skip this patch)"));
status_printf_ln(s, color,
@@ -1011,7 +1011,7 @@ static void show_rebase_in_progress(struct wt_status *s,
_("You are currently rebasing."));
if (s->hints)
status_printf_ln(s, color,
- _(" (all conflicts fixed: run \"git rebase --continue\")"));
+ _(" (all conflicts fixed: use \"git rebase --continue\" to continue)"));
} else if (split_commit_in_progress(s)) {
if (state->branch)
status_printf_ln(s, color,
@@ -1023,7 +1023,7 @@ static void show_rebase_in_progress(struct wt_status *s,
_("You are currently splitting a commit during a rebase."));
if (s->hints)
status_printf_ln(s, color,
- _(" (Once your working directory is clean, run \"git rebase --continue\")"));
+ _(" (Once your working directory is clean, use \"git rebase --continue\" to continue)"));
} else {
if (state->branch)
status_printf_ln(s, color,
@@ -1052,10 +1052,10 @@ static void show_cherry_pick_in_progress(struct wt_status *s,
if (s->hints) {
if (has_unmerged(s))
status_printf_ln(s, color,
- _(" (fix conflicts and run \"git cherry-pick --continue\")"));
+ _(" (fix conflicts and use \"git cherry-pick --continue\" to continue)"));
else
status_printf_ln(s, color,
- _(" (all conflicts fixed: run \"git cherry-pick --continue\")"));
+ _(" (all conflicts fixed: use \"git cherry-pick --continue\" to continue)"));
status_printf_ln(s, color,
_(" (use \"git cherry-pick --abort\" to cancel the cherry-pick operation)"));
}
@@ -1071,10 +1071,10 @@ static void show_revert_in_progress(struct wt_status *s,
if (s->hints) {
if (has_unmerged(s))
status_printf_ln(s, color,
- _(" (fix conflicts and run \"git revert --continue\")"));
+ _(" (fix conflicts and use \"git revert --continue\" to continue)"));
else
status_printf_ln(s, color,
- _(" (all conflicts fixed: run \"git revert --continue\")"));
+ _(" (all conflicts fixed: use \"git revert --continue\" to continue)"));
status_printf_ln(s, color,
_(" (use \"git revert --abort\" to cancel the revert operation)"));
}
--
1.9.0.174.g6f75b8f
next prev parent reply other threads:[~2014-03-14 4:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 4:37 [PATCH 0/3] Make git more user-friendly during a merge conflict Andrew Wong
2014-03-14 4:37 ` Andrew Wong [this message]
2014-03-17 21:51 ` [PATCH 1/3] wt-status: Make status messages more consistent with others Junio C Hamano
2014-03-14 4:37 ` [PATCH 2/3] merge: Advise user to use "git merge --abort" to abort merges Andrew Wong
2014-03-17 21:58 ` Junio C Hamano
2014-03-14 4:37 ` [PATCH 3/3] reset: Print a warning when user uses "git reset" during a merge Andrew Wong
2014-03-14 14:33 ` Marc Branchaud
2014-03-14 17:04 ` Andrew Wong
2014-03-14 20:55 ` Junio C Hamano
2014-03-14 21:35 ` Andrew Wong
2014-03-15 19:23 ` Marc Branchaud
2014-03-17 21:54 ` Junio C Hamano
2014-03-17 23:04 ` [PATCH 0/3] Make git more user-friendly during a merge conflict Junio C Hamano
2014-03-17 23:25 ` Andrew Wong
2014-03-19 22:30 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1394771872-25940-2-git-send-email-andrew.kw.w@gmail.com \
--to=andrew.kw.w@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).