From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 1/2] textual: fix the usage message of kill
Date: Mon, 14 Jul 2014 16:17:09 +0200 [thread overview]
Message-ID: <20140714141709.GK30288@x2.net.home> (raw)
In-Reply-To: <1405346109.2706.141424829.357CACFE@webmail.messagingengine.com>
On Mon, Jul 14, 2014 at 03:55:09PM +0200, Benno Schulenberg wrote:
>
> On Mon, Jul 14, 2014, at 15:48, Karel Zak wrote:
> > On Wed, Jul 09, 2014 at 03:29:09PM +0200, Benno Schulenberg wrote:
> > > misc-utils/kill.c | 20 ++++++++++----------
> > > 1 files changed, 10 insertions(+), 10 deletions(-)
> >
> > I guess we want to merge this patch (that modifies already translated
> > strings) after release, right?
>
> Don't know... Better do it now, so you can also apply Sami's patch
> and have things working correctly. Very few people will be using
> this version of kill, so few will experience missing translations.
Well, procps version is deprecated in favour of kill(1) from u-l ;-)
(The built-in shell kill command is another story.)
> It's a pity that it invalidates already translated strings, but it
> can't be helped. It's kind of my fault; I should have had a look
> at rc-1.
Yep, it would be nice to found a way how to solve this kind of problem
next time, almost always we have bug reports from translators, but
it's too late...
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-07-14 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:29 [PATCH 1/2] textual: fix the usage message of kill Benno Schulenberg
2014-07-09 13:29 ` [PATCH 2/2] docs: fix many wording and some formatting issues in the man page " Benno Schulenberg
2014-07-14 13:53 ` Karel Zak
2014-07-14 13:48 ` [PATCH 1/2] textual: fix the usage message " Karel Zak
2014-07-14 13:55 ` Benno Schulenberg
2014-07-14 14:17 ` Karel Zak [this message]
2014-07-14 14:44 ` Benno Schulenberg
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=20140714141709.GK30288@x2.net.home \
--to=kzak@redhat.com \
--cc=bensberg@justemail.net \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox