From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@telfort.nl>
Cc: util-linux@vger.kernel.org, Petr Pisar <petr.pisar@atlas.cz>
Subject: Re: [PATCH 1/2] textual: fix some typos and inconsistencies in usage and error messages
Date: Mon, 29 Apr 2024 21:38:02 +0200 [thread overview]
Message-ID: <20240429193802.cflzk47hgjrlsq5f@ws.net.home> (raw)
In-Reply-To: <4582ffa0-e5fb-42ca-9b4f-a6a0bc67bed2@telfort.nl>
On Mon, Apr 29, 2024 at 04:58:35PM +0200, Benno Schulenberg wrote:
>
> Op 29-04-2024 om 14:35 schreef Karel Zak:
> > Applied (to master and stable/v2.40), thanks!
>
> Hmm... I don't think it's a good idea to apply it to the stable/v2.40
> branch, as it invalidates any translations that were made for these
> strings. It would be okay if you first offer a new POT file to the
> TP before making the next stable dot release.
Good point. I believe we can begin implementing rc1 for stable
releases, with a short period of time for translators to make any
necessary changes. For instance, we could release rc1 on Wednesday and
the final version on Monday.
Since the stable/ branch is now being more actively maintained, it
would be beneficial to involve TP in the process too.
Does it make sense?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2024-04-29 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 15:48 [PATCH 1/2] textual: fix some typos and inconsistencies in usage and error messages Benno Schulenberg
2024-03-26 15:48 ` [PATCH 2/2] lastlog2: begin descriptions of options with a lowercase letter Benno Schulenberg
2024-04-29 12:35 ` [PATCH 1/2] textual: fix some typos and inconsistencies in usage and error messages Karel Zak
2024-04-29 14:58 ` Benno Schulenberg
2024-04-29 19:38 ` Karel Zak [this message]
2024-04-30 14:07 ` Benno Schulenberg
2024-05-01 20:53 ` Karel Zak
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=20240429193802.cflzk47hgjrlsq5f@ws.net.home \
--to=kzak@redhat.com \
--cc=bensberg@telfort.nl \
--cc=petr.pisar@atlas.cz \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).