From: Andy Whitcroft <apw@shadowen.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] Improve cached content header of status output
Date: Fri, 05 Jan 2007 13:14:21 +0000 [thread overview]
Message-ID: <459E4F2D.4000806@shadowen.org> (raw)
In-Reply-To: <7vr6u9g1l4.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andy Whitcroft <apw@shadowen.org> writes:
>
>>> +static void wt_status_print_cached_header(const char *reference)
>>> +{
>>> + const char *c = color(WT_STATUS_HEADER);
>>> + color_printf_ln(c, "# Cached changes to be committed:");
>>> ...
>> We seem to be using 'Cached' and 'staged' here. I thought we had
>> updated all the docs to call files in the index "Staged for commit".
>
> # Changes staged to be committed:
>
> Somebody did not like the verb "stage"; perhaps we can say:
>
> # You have added changes to these files to be committed:
> ...
# These files have changes and are marked for commit:
> # There are yet to be added changes to these files:
# These files have changes but are not marked for commit:
> ...
-apw
next prev parent reply other threads:[~2007-01-05 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 19:26 [PATCH/RFC] Assorted small changes to runstatus Juergen Ruehle
2007-01-02 19:26 ` [PATCH 1/4] Clarify syntax and role of git-add in status output Juergen Ruehle
2007-01-02 19:26 ` [PATCH 2/4] Improve cached content header of " Juergen Ruehle
2007-01-05 10:54 ` Andy Whitcroft
2007-01-05 11:22 ` Junio C Hamano
2007-01-05 13:14 ` Andy Whitcroft [this message]
2007-01-05 17:14 ` Juergen Ruehle
2007-01-05 18:42 ` Junio C Hamano
2007-01-08 13:28 ` Andy Whitcroft
2007-01-08 14:27 ` Juergen Ruehle
2007-01-02 19:26 ` [PATCH 3/4] Improve "nothing to commit" part " Juergen Ruehle
2007-01-02 19:26 ` [PATCH 4/4] Support --amend on initial commit in " Juergen Ruehle
2007-01-03 2:51 ` [PATCH/RFC] Assorted small changes to runstatus Junio C Hamano
2007-01-03 5:34 ` Juergen Ruehle
2007-01-07 19:18 ` [PATCH] Remove unnecessary git-rm --cached reference from status output Juergen Ruehle
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=459E4F2D.4000806@shadowen.org \
--to=apw@shadowen.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).