From: Milan Broz <gmazyland@gmail.com>
To: Petr Pisar <petr.pisar@atlas.cz>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup 1.5.0-rc2 messages questions
Date: Mon, 25 Jun 2012 22:38:14 +0200 [thread overview]
Message-ID: <4FE8CC36.10709@gmail.com> (raw)
In-Reply-To: <20120625190846.GA3325@album.bayer.uni.cx>
On 06/25/2012 09:08 PM, Petr Pisar wrote:
> while updating Czech translation for cryptsetup 1.5.0-rc2, I found few issues
> I'd like to clarify.
There will be more cleanups needed, I added that to rc2 because this reencryption
tool can be useful for several people but it is still experimental.
Let me know if there are other changes needed.
(I guess ping on IRC works better in this case ;-)
> poptSetOtherOptionHelp(popt_context, N_("[OPTION...] <device>"));
Hm. Then same problem is then in cryptsetup for years:
N_("[OPTION...] <action> <action-specific>"));
> (2) It think message
>
> #: src/cryptsetup_reencrypt.c:451
> #, c-format
> msgid "Log file %s exists, restarting reencryption.\n"
>
> should be rephrased to `resuming reencryption' if I understand the
> reencryption log correctly. `Restarting' means drop everything what has been
> done till now and start again from the begining.
yes, I am using "suspending reencryption" elsewhere so resuming is definitely better.
> (3) There is missing space after the number 1.
> #: src/cryptsetup_reencrypt.c:1288
> msgid "Only values between 1MiB and 64 MiB allowed for reencryption block size."
ok, I'll change that.
Thanks,
Milan
next prev parent reply other threads:[~2012-06-25 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 19:08 [dm-crypt] cryptsetup 1.5.0-rc2 messages questions Petr Pisar
2012-06-25 20:38 ` Milan Broz [this message]
2012-06-26 18:38 ` Petr Pisar
2012-06-26 18:41 ` [dm-crypt] [PATCH] Pass help text to popt already translated Petr Písař
2012-06-26 19:29 ` Milan Broz
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=4FE8CC36.10709@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=petr.pisar@atlas.cz \
/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