git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-gui wording suggestions

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jul 27, 2007, 04:40 UTC
Message-ID
<20070727044009.GF20052@spearce.org>
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. :-|

Show 14 quoted lines
> 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.
Previous: Christian StimmingNext: Junio C Hamano
Message 2 of 6 in “git-gui wording suggestions”
  1. git-gui wording suggestionsChristian Stimming, Jul 26, 2007
  2. Shawn O. PearceJul 27, 2007
  3. Junio C HamanoJul 27, 2007
  4. Christian StimmingJul 27, 2007
  5. Christian StimmingJul 28, 2007
  6. Shawn O. PearceJul 29, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.