From: Junio C Hamano <gitster@pobox.com>
To: Fangyi Zhou <me@fangyi.io>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: fz/rebase-msg-update (2023-02-27)
Date: Tue, 07 Mar 2023 13:52:56 -0800 [thread overview]
Message-ID: <xmqqa60ow7nr.fsf@gitster.g> (raw)
In-Reply-To: <37ed877d5927c7cebba7e47769be3a069eacd6c6.camel@fangyi.io> (Fangyi Zhou's message of "Tue, 07 Mar 2023 21:48:31 +0000")
Fangyi Zhou <me@fangyi.io> writes:
> On Tue, 2023-03-07 at 13:09 -0800, Junio C Hamano wrote:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>> > Fangyi Zhou <me@fangyi.io> writes:
>> >
>> > > This patch is actually a hotfix for a topic added in v2.40.0 RC
>> > > 2c6e5b32aa (Merge branch 'en/rebase-incompatible-opts', 2023-02-
>> > > 03),
>> > > could it be reviewed and included in the release?
>> >
>> > Is it?
>> >
>> > If a message used to say autoSquash 2.39 series and 2.40-rc2
>> > has it autosquash, then it may be a hotfix, but otherwise no.
>>
>> Besides, localizaiton teams are already working on what has been
>> in 'master'; it disrupts their workflow to change end-user message
>> under them.
>
> The patch fixes a newly added i18n string, not the option itself,
> see
> https://github.com/git-l10n/pot-changes/blob/pot/main/2023-02-04.diff
> I found the issue while conducting the localisation for v2.40.0.
Exactly. That's not a regression.
next prev parent reply other threads:[~2023-03-07 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 17:50 What's cooking in git.git (Mar 2023, #01; Wed, 1) Junio C Hamano
2023-03-07 21:04 ` fz/rebase-msg-update (2023-02-27) (Was: What's cooking in git.git (Mar 2023, #01; Wed, 1)) Fangyi Zhou
2023-03-07 21:06 ` fz/rebase-msg-update (2023-02-27) Junio C Hamano
2023-03-07 21:09 ` Junio C Hamano
2023-03-07 21:48 ` Fangyi Zhou
2023-03-07 21:52 ` Junio C Hamano [this message]
2023-03-08 20:59 ` Junio C Hamano
2023-03-08 21:38 ` Fangyi Zhou
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=xmqqa60ow7nr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@fangyi.io \
--cc=newren@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.