From: Alex Riesen <raa.lkml@gmail.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Pat Thoyts <patthoyts@users.sourceforge.net>,
Serge Ziryukin <ftrvxmtrx@gmail.com>,
Dmitry Potapov <dpotapov@gmail.com>,
Alexander Gavrilov <angavrilov@gmail.com>
Subject: [PATCH 0/3] git-gui: update russian translation
Date: Mon, 17 Jan 2011 22:08:20 +0100 [thread overview]
Message-ID: <20110117210820.GA27029@blimp.localdomain> (raw)
Thanks to Skip, who reminded me of the russian translation, here is a very
small collection of still applicable patches I collected in mailing list
archives. The ru.po is also updated.
Alex Riesen (1):
git-gui: update russian translation
Serge Ziryukin (1):
fix git-gui russian translation typos
Skip (1):
git-gui: spelling fixes in russian translation
po/ru.po | 623 ++++++++++++++++++++++++++++++++------------------------------
1 files changed, 321 insertions(+), 302 deletions(-)
--
1.7.3.4.643.g8fb2b
next reply other threads:[~2011-01-17 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:08 Alex Riesen [this message]
2011-01-17 21:16 ` [PATCH 0/3] git-gui: update russian translation Alex Riesen
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=20110117210820.GA27029@blimp.localdomain \
--to=raa.lkml@gmail.com \
--cc=angavrilov@gmail.com \
--cc=dpotapov@gmail.com \
--cc=ftrvxmtrx@gmail.com \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.net \
--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).