From: Pierre Habouzit <madcoder@debian.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: [PATCH v2] status: display "doing what" information in git status
Date: Fri, 6 May 2011 19:36:56 +0200 [thread overview]
Message-ID: <20110506173656.GA2872@madism.org> (raw)
In-Reply-To: <7vei4b20we.fsf@alter.siamese.dyndns.org>
On Fri, May 06, 2011 at 10:29:21AM -0700, Junio C Hamano wrote:
> Pierre Habouzit <madcoder@debian.org> writes:
>
> > $ git status
> > # in the middle of a git rebase -i of master (detached head)
> > ...
> > # qkv/A/
> > no changes added to commit (use "git add" and/or "git commit -a")
> >
> > If we have an ongoing operation then:
> > - if we are on a branch it displays:
> > # On branch $branch ($what_is_ongoing)
> > # ($ongoing_hint)
> > - if we are on a detached head it displays:
> > # $what_is_ongoing (detached head)
> > # ($ongoing_hint)
>
> I'll reindent the above to align these example output the earlier output sample
> when I apply them.
Sure.
> > + const char * const rebase_advice =
> > + _("use \"git rebase --abort\" to abort current rebase or proceed");
> > + const char * const am_advice =
> > + _("use \"git am --abort\" to abort current mailbox apply or proceed");
>
> If the reader does not even know that the "--abort" option is used to
> abort, " or proceed" needs to be followed by "by doing $this", if it wants
> to have any practical value. I would suggest dropping it.
>
> > + const char * const merge_advice =
> > + _("use \"git reset --hard\" to abort, or resolve conflicts and commit");
> This codepath being in wt-status.c, I wonder if any of these advices could
> trigger to appear in the log message editor when the user tries to run
> "git commit". If so, I suspect any of the above is too late to help the
> user, no?
Well I'm not very happy with the advices, feel free to reword them in a better
way.
> Also, should we make these conditional upon advice.status or something?
they are
vvvvvvvvvvvvvvvvvvv
+ if (advice && advice_status_hints) {
+ status_printf(s, color(WT_STATUS_HEADER, s), "");
+ status_printf_more(s, status_nobranch, " (%s)\n", advice);
+ }
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
next prev parent reply other threads:[~2011-05-06 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 21:48 [PATCH 1/1] status: display "doing what" information in git status Pierre Habouzit
2011-05-05 23:06 ` Sverre Rabbelier
2011-05-05 23:26 ` Pierre Habouzit
2011-05-06 7:48 ` Michael J Gruber
2011-05-06 8:04 ` Pierre Habouzit
2011-05-05 23:37 ` Junio C Hamano
2011-05-05 23:39 ` Pierre Habouzit
2011-05-05 23:47 ` Pierre Habouzit
2011-05-05 23:49 ` Junio C Hamano
2011-05-05 23:51 ` Pierre Habouzit
2011-05-06 7:38 ` [PATCH v2] " Pierre Habouzit
2011-05-06 10:13 ` Jakub Narebski
2011-05-06 17:40 ` Pierre Habouzit
2011-05-06 17:29 ` Junio C Hamano
2011-05-06 17:36 ` Pierre Habouzit [this message]
2011-05-06 18:24 ` Junio C Hamano
2011-05-06 18:40 ` Matthieu Moy
2011-05-06 18:44 ` Pierre Habouzit
2011-05-06 19:15 ` Matthieu Moy
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=20110506173656.GA2872@madism.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).