From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Re: RFC: German translation vocabulary
Date: Sun, 16 Sep 2007 22:21:34 +0200 [thread overview]
Message-ID: <87y7f6fjjl.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <200709161438.37733.stimming@tuhh.de> (Christian Stimming's message of "Sun, 16 Sep 2007 14:38:37 +0200")
* Christian Stimming:
> repository - Projektarchiv
"Projekt" or "Archiv" should suffice.
> revision - Version
"Versionsangabe", probably. I think "revision" is most used as a
short form of "revision specifier".
> staging area - Bereitstellung
"Index"?
> branch [noun] - Zweig
> branch [verb] - verzweigen
Or "abzweigen", if it's used transitive.
> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)
I came up with David's "Beschreibung" independently. It fits better
to "Sammlung" below than "Zusammenfassung", IMHO.
> For some of them you can see alternatives considered in the glossary [1], but
> overall the above ones were rather easy. Now for the difficult ones:
>
> commit [noun]
> commit [verb]
"Sammlung" and "sammeln".
> checkout [noun]
> checkout [verb]
How's a checkout different from a working copy?
But to be honest, I wouldn't translate "repository" and "commit", at
least if they are used as nouns.
next prev parent reply other threads:[~2007-09-16 20:21 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
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 ` Florian Weimer [this message]
2007-09-16 21:37 ` RFC: German " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y7f6fjjl.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.