git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: git <git@vger.kernel.org>, Lucien.Kong@ensimag.imag.fr
Subject: Re: [PATCH] wt-status: give better advice when cherry-pick is in progress
Date: Mon, 17 Jun 2013 13:15:58 -0700	[thread overview]
Message-ID: <7vli68biip.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAN0XMOJhUA7Uut-jpnpSRW_E2xHARCyP_8FUmebNjBkm59v0JA@mail.gmail.com> (Ralf Thielow's message of "Mon, 17 Jun 2013 21:29:04 +0200")

Ralf Thielow <ralf.thielow@gmail.com> writes:

> 2013/6/17 Junio C Hamano <gitster@pobox.com>:
>> Ralf Thielow <ralf.thielow@gmail.com> writes:
>>
>>> When cherry-pick is in progress, 'git status' gives the advice to
>>> run "git commit" to finish the cherry-pick. However, this won't continue
>>> the sequencer.
>>> "git status" should give the advice of running "git cherry-pick --continue"
>>> or "git cherry-pick --abort".
>>
>> Is the above _always_ the case, or does the updated advice message
>> only apply when you are cherry-picking a range of commits with "git
>> cherry-pick A..B"?  In other words, when "git cherry-pick $it" (a
>> single commit) stops, waiting for your help to resolve it, would
>> "git cherry-pick --continue" conclude it?
>>
>
> Yes, both "--continue" and "--abort" works with a single commit.

Perhaps that is a good thing to explain, in addition to "won't
continue the sequencer", as single-pick case does not have much to
do with it ;-)

Thanks, will queue.

>> If that works then this definitely is a good change (the user only
>> needs to know "cherry-pick --continue").
>>
>>> Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
>>> ---
>>>  t/t7512-status-help.sh | 6 ++++--
>>>  wt-status.c            | 6 ++++--
>>>  2 files changed, 8 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/t/t7512-status-help.sh b/t/t7512-status-help.sh
>>> index bf08d4e..4f09bec 100755
>>> --- a/t/t7512-status-help.sh
>>> +++ b/t/t7512-status-help.sh
>>> @@ -632,7 +632,8 @@ test_expect_success 'status when cherry-picking before resolving conflicts' '
>>>       cat >expected <<-\EOF &&
>>>       # On branch cherry_branch
>>>       # You are currently cherry-picking.
>>> -     #   (fix conflicts and run "git commit")
>>> +     #   (fix conflicts and run "git cherry-pick --continue")
>>> +     #   (use "git cherry-pick --abort" to cancel the cherry-pick operation)
>>>       #
>>>       # Unmerged paths:
>>>       #   (use "git add <file>..." to mark resolution)
>>> @@ -655,7 +656,8 @@ test_expect_success 'status when cherry-picking after resolving conflicts' '
>>>       cat >expected <<-\EOF &&
>>>       # On branch cherry_branch
>>>       # You are currently cherry-picking.
>>> -     #   (all conflicts fixed: run "git commit")
>>> +     #   (all conflicts fixed: run "git cherry-pick --continue")
>>> +     #   (use "git cherry-pick --abort" to cancel the cherry-pick operation)
>>>       #
>>>       # Changes to be committed:
>>>       #
>>> diff --git a/wt-status.c b/wt-status.c
>>> index bf84a86..438a40d 100644
>>> --- a/wt-status.c
>>> +++ b/wt-status.c
>>> @@ -955,10 +955,12 @@ static void show_cherry_pick_in_progress(struct wt_status *s,
>>>       if (advice_status_hints) {
>>>               if (has_unmerged(s))
>>>                       status_printf_ln(s, color,
>>> -                             _("  (fix conflicts and run \"git commit\")"));
>>> +                             _("  (fix conflicts and run \"git cherry-pick --continue\")"));
>>>               else
>>>                       status_printf_ln(s, color,
>>> -                             _("  (all conflicts fixed: run \"git commit\")"));
>>> +                             _("  (all conflicts fixed: run \"git cherry-pick --continue\")"));
>>> +             status_printf_ln(s, color,
>>> +                     _("  (use \"git cherry-pick --abort\" to cancel the cherry-pick operation)"));
>>>       }
>>>       wt_status_print_trailer(s);
>>>  }

      reply	other threads:[~2013-06-17 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  4:28 [PATCH] wt-status: give better advice when cherry-pick is in progress Ralf Thielow
2013-06-17 19:18 ` Junio C Hamano
2013-06-17 19:29   ` Ralf Thielow
2013-06-17 20:15     ` Junio C Hamano [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vli68biip.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Lucien.Kong@ensimag.imag.fr \
    --cc=git@vger.kernel.org \
    --cc=ralf.thielow@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).