From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de>
Cc: David Kastrup <dak@gnu.org>, git@vger.kernel.org
Subject: Re: RFC: German translation vocabulary
Date: Mon, 17 Sep 2007 10:17:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709171013230.28586@racer.site> (raw)
In-Reply-To: <20070917075433.GF17021@cip.informatik.uni-erlangen.de>
Hi,
On Mon, 17 Sep 2007, Alexander Wuerstlein wrote:
> On 070916 23:34, David Kastrup <dak@gnu.org> wrote:
> > Alexander Wuerstlein <snalwuer@cip.informatik.uni-erlangen.de> writes:
> >
> > > On 070916 14:46, Christian Stimming <stimming@tuhh.de> wrote:
> > >> msgid "commit [noun]"
> > >> msgstr "?bertragung (Sendung?, ?bergabe?, Einspielung?, Ablagevorgang?)"
> > >
> > > "Vorgang"? (think Beamtendeutsch)
> >
> > Buchung, Einbuchung, Verbuchung, Registrierung?
>
> Transaktion?
The real problem is that we use "commit" in two senses:
- the action ("to commit", but also, "to do a commit") of making a new
revision, but also
- the revision in the revision graph ("is this in the commit abcdef?").
So I do not think that any proposals reflect the ambiguity of "a commit".
I actually talk about "Revision" in German, when I refer to a commit.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-17 9:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 12:38 RFC: German translation vocabulary Christian Stimming
2007-09-16 15:01 ` David Soria
2007-09-16 15:07 ` David Kastrup
2007-09-16 15:08 ` David Kastrup
2007-09-16 15:12 ` David Soria
2007-09-16 17:23 ` Alexander Wuerstlein
2007-09-16 21:34 ` David Kastrup
2007-09-17 7:54 ` Alexander Wuerstlein
2007-09-17 9:17 ` Johannes Schindelin [this message]
2007-09-17 19:09 ` Christian Stimming
2007-09-17 12:42 ` David Kastrup
2007-09-16 19:44 ` Simon Richter
2007-09-16 21:36 ` David Kastrup
2007-09-16 20:11 ` RFC: Italian " Michele Ballabio
2007-09-16 20:21 ` RFC: German " Florian Weimer
2007-09-16 21:37 ` David Kastrup
2007-09-17 19:45 ` Christian Stimming
2007-09-17 19:56 ` Florian Weimer
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0709171013230.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=snalwuer@cip.informatik.uni-erlangen.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).