From: Junio C Hamano <gitster@pobox.com>
To: Peter Karlsson <peter@softwolves.pp.se>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Steffen Prohaska <prohaska@zib.de>,
"Shawn O. Pearce" <spearce@spearce.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: How to run git-gui always in English?
Date: Tue, 30 Oct 2007 01:56:51 -0700 [thread overview]
Message-ID: <7vbqahm14c.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0710291357420.23695@perkele.intern.softwolves.pp.se> (Peter Karlsson's message of "Mon, 29 Oct 2007 13:58:26 +0100 (CET)")
Peter Karlsson <peter@softwolves.pp.se> writes:
> Alex Riesen:
>
>> Because you do not send changes to a _server_. There is no
>> server. There is just another repo. Hence just "push"
>
> Fine. "Send to repository", then. My point is that if "push" is a
> technical term, then it doesn't belong in the GUI, and if it isn't,
> then it should be translated like any other UI element.
Why doesn't a "technical term" belong in the GUI in the first
place?
If majority of people who use git know and use the term "push"
to describe that concept, certainly they will be the people from
whom the new people who start to use git (either from command
line or from GUI) get help. Why do you want to have them use
different language to make the communication more difficult?
next prev parent reply other threads:[~2007-10-30 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 6:47 How to run git-gui always in English? Steffen Prohaska
2007-10-21 6:52 ` Shawn O. Pearce
2007-10-21 7:03 ` Steffen Prohaska
2007-10-21 7:15 ` Shawn O. Pearce
2007-10-23 20:00 ` Steffen Prohaska
2007-10-23 22:45 ` Shawn O. Pearce
2007-10-26 8:00 ` Peter Karlsson
2007-10-26 21:41 ` Alex Riesen
2007-10-29 12:58 ` Peter Karlsson
2007-10-30 8:56 ` Junio C Hamano [this message]
2007-10-30 9:58 ` Johannes Schindelin
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=7vbqahm14c.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
--cc=prohaska@zib.de \
--cc=raa.lkml@gmail.com \
--cc=spearce@spearce.org \
/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).