From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2024, #08; Mon, 23)
Date: Thu, 26 Dec 2024 08:05:50 -0800 [thread overview]
Message-ID: <xmqqv7v6xwdd.fsf@gitster.g> (raw)
In-Reply-To: <edd2807e-4b2b-48d3-97e0-19b3a0dcab8f@kdbg.org> (Johannes Sixt's message of "Tue, 24 Dec 2024 12:55:56 +0100")
Johannes Sixt <j6t@kdbg.org> writes:
> Am 23.12.24 um 20:27 schrieb Junio C Hamano:
>> Let's wait for git-gui, gitk, and possibly po/ and delay the tagging
>> of the -rc1.
>
> I've just sent a pull request for Git GUI to make the current master
> better visible for translators. Gitk is already up-to-date.
>
> I'll wait a week or so for translations to trickle in and then send
> another round of pull requests. Is this a practical workflow?
Yeah, it is that really slow part of the year now, so it would not
make much sense to have rc releases without much changes in them.
Let's have -rc1 on Monday, -rc2 after a week, and the final later on
the same week.
Thanks.
prev parent reply other threads:[~2024-12-26 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 19:27 What's cooking in git.git (Dec 2024, #08; Mon, 23) Junio C Hamano
2024-12-24 11:55 ` Johannes Sixt
2024-12-26 16:05 ` Junio C Hamano [this message]
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=xmqqv7v6xwdd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.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).