From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Christian Stimming <stimming@tuhh.de>,
Brett Schwarz <brett_schwarz@yahoo.com>,
git@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] git-gui wording suggestions
Date: Thu, 26 Jul 2007 22:09:37 -0700 [thread overview]
Message-ID: <7vvec64elq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070727044009.GF20052@spearce.org> (Shawn O. Pearce's message of "Fri, 27 Jul 2007 00:40:09 -0400")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Christian Stimming <stimming@tuhh.de> wrote:
>> Unifiy wording to say "to stage" instead of "to add" always.
> ...
>> With this patch I'd propose to talk every only about "stage" instead
>> of "add". IMHO that's just the logical conclusion of the above wording
>> decision. What do you think?
>
> Yes, I agree. This is a necessary change, the current wording is
> very confusing.
Looking at the expressions used in the application from the
point of view of translating the words to (or expressing the
concept in) another language helps finding more appropriate
wording even in the original language.
"Add" is a simple and nice word, but it is too broad, so "to
stage" is an improvement. The translated message for "to stage"
for Japanese we will probably end up choosing would translate
back to English as "Schedule for commit".
next prev parent reply other threads:[~2007-07-27 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 9:19 [PATCH] git-gui wording suggestions Christian Stimming
2007-07-27 4:40 ` Shawn O. Pearce
2007-07-27 5:09 ` Junio C Hamano [this message]
2007-07-27 11:42 ` Christian Stimming
[not found] ` <861wevqz7d.fsf@lola.quinscape.zz>
2007-07-28 20:17 ` [PATCH] git-gui.git: Wording suggestions, 2nd try Christian Stimming
2007-07-29 7:08 ` Shawn O. Pearce
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=7vvec64elq.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=brett_schwarz@yahoo.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--cc=spearce@spearce.org \
--cc=stimming@tuhh.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.