From: "Shawn O. Pearce" <spearce@spearce.org>
To: Christian Stimming <stimming@tuhh.de>
Cc: Brett Schwarz <brett_schwarz@yahoo.com>,
git@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] git-gui wording suggestions
Date: Fri, 27 Jul 2007 00:40:09 -0400 [thread overview]
Message-ID: <20070727044009.GF20052@spearce.org> (raw)
In-Reply-To: <20070726111902.xqkxcdlsbo8w4c8k@webmail.tu-harburg.de>
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. I would apply this earlier than the other i18n
stuff, but this patch is written based upon the current i18n work.
:-|
> diff --git a/git-gui.sh b/git-gui.sh
> index 3536d38..fd8b4b4 100755
> --- a/git-gui.sh
> +++ b/git-gui.sh
> @@ -1824,12 +1824,12 @@ if {[is_enabled multicommit] || [is_enabled
> singlecommit]} {
> lappend disable_on_lock \
> [list .mbar.commit entryconf [.mbar.commit index last] -state]
>
> - .mbar.commit add command -label [mc "Add To Commit"] \
> + .mbar.commit add command -label [mc "Stage To Commit"] \
> -command do_add_selection
> lappend disable_on_lock \
> [list .mbar.commit entryconf [.mbar.commit index last] -state]
...
--
Shawn.
next prev parent reply other threads:[~2007-07-27 4:40 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 [this message]
2007-07-27 5:09 ` Junio C Hamano
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=20070727044009.GF20052@spearce.org \
--to=spearce@spearce.org \
--cc=brett_schwarz@yahoo.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.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 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).