From: Alex Riesen <raa.lkml@gmail.com>
To: Peter Karlsson <peter@softwolves.pp.se>
Cc: 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: Fri, 26 Oct 2007 23:41:24 +0200 [thread overview]
Message-ID: <20071026214124.GB3062@steel.home> (raw)
In-Reply-To: <Pine.LNX.4.62.0710260857210.3542@perkele.intern.softwolves.pp.se>
Peter Karlsson, Fri, Oct 26, 2007 10:00:32 +0200:
> Steffen Prohaska:
>
>> There are a lot of efforts going on to localize git-gui, including
>> technical terms like "push". Personally I don't understand what this
>> should be useful for. The command is called "git push"s. So, why should it
>> be named differently in the gui.
>
> Not that I agree that "push" is a technical word, but perhaps you have a
> point. Why should there be such words in the GUI to start with? It's a GUI,
> trying to abstract away the command line. Why not have a button "Send" or a
> menu entry "Send changes to server", mimicing the "git push" command line
> option? Using command line names or showing protocol data directly in a
> user-oriented GUI is most often a bad idea.
>
> Or perhaps what we need is an actual translation from "gitish" to English,
> which would have
>
> msgid "Push"
> msgstr "Send changes to server"
>
Because you do not send changes to a _server_. There is no server.
There is just another repo. Hence just "push"
next prev parent reply other threads:[~2007-10-26 21:41 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 [this message]
2007-10-29 12:58 ` Peter Karlsson
2007-10-30 8:56 ` Junio C Hamano
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=20071026214124.GB3062@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
--cc=prohaska@zib.de \
--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).