From: Phillip Sz <phillip.szelat@gmail.com>
To: Ralf Thielow <ralf.thielow@gmail.com>, git@vger.kernel.org
Cc: tr@thomasrast.ch, jk@jk.gs, stimming@tuhh.de,
matthias.ruester@gmail.com, magnus.goerlitz@googlemail.com
Subject: Re: [PATCH 1/7] part1: l10n: de.po: use imperative form for command options
Date: Fri, 19 Sep 2014 21:11:51 +0200 [thread overview]
Message-ID: <541C7FF7.1020105@gmail.com> (raw)
In-Reply-To: <1411146770-8508-2-git-send-email-ralf.thielow@gmail.com>
Hi,
> #: archive.c:351 builtin/archive.c:91
> msgid "retrieve the archive from remote repository <repo>"
> -msgstr "ruft das Archiv von Remote-Repository <Repository> ab"
> +msgstr "Archiv von Remote-Repository <Repository> abrufen"
>
"Archiv vom Remote-Repository <Repository> abrufen" sounds better to me.
> #: builtin/add.c:256
> msgid "record only the fact that the path will be added later"
> -msgstr "speichert nur, dass der Pfad später hinzugefügt werden soll"
> +msgstr "nur speichern, dass der Pfad später hinzugefügt werden soll"
>
"nur speichern, so dass der Pfad später hinzugefügt werden soll" maybe
use a full sentence?
> #: builtin/apply.c:4378
> msgid "instead of applying the patch, see if the patch is applicable"
> @@ -2472,27 +2472,27 @@ msgstr ""
> #: builtin/apply.c:4380
> msgid "make sure the patch is applicable to the current index"
> msgstr ""
> -"stellt sicher, dass der Patch in der aktuellen Staging-Area angewendet "
> +"sicher stellen, dass der Patch in der aktuellen Staging-Area angewendet "
> "werden kann"
>
"stellen Sie sicher, dass der Patch in der aktuellen Staging-Area
angewendet "
"werden kann" Someone is addressed dirctly.
Phillip
next prev parent reply other threads:[~2014-09-19 19:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 17:12 [PATCH 0/7] l10n: de.po: use imperative form for command options Ralf Thielow
2014-09-19 17:12 ` [PATCH 1/7] part1: " Ralf Thielow
2014-09-19 19:11 ` Phillip Sz [this message]
2014-09-19 20:43 ` Ralf Thielow
2014-10-24 18:02 ` [PATCH v2] " Ralf Thielow
2014-10-25 8:53 ` phillip
2014-09-19 17:12 ` [PATCH 2/7] part2: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 3/7] part3: " Ralf Thielow
2014-09-23 10:24 ` Phillip Sz
2014-09-25 18:04 ` Ralf Thielow
2014-09-25 19:45 ` phillip
2014-10-24 18:02 ` [PATCH v2] " Ralf Thielow
2014-09-19 17:12 ` [PATCH 4/7] part4: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 5/7] part5: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 6/7] part6: " Ralf Thielow
2014-09-19 17:12 ` [PATCH 7/7] part7: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 0/7] use imperative form for command Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 1/7] part1: l10n: de.po: use imperative form for command options Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 2/7] part2: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 3/7] part3: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 4/7] part4: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 5/7] part5: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 6/7] part6: " Ralf Thielow
2014-11-07 20:11 ` [PATCH v3 7/7] part7: " Ralf Thielow
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=541C7FF7.1020105@gmail.com \
--to=phillip.szelat@gmail.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=magnus.goerlitz@googlemail.com \
--cc=matthias.ruester@gmail.com \
--cc=ralf.thielow@gmail.com \
--cc=stimming@tuhh.de \
--cc=tr@thomasrast.ch \
/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).