From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: What's cooking in git.git (Feb 2022, #02; Wed, 9)
Date: Fri, 11 Feb 2022 22:01:44 +0100 [thread overview]
Message-ID: <1886649.yonrKIyjYj@cayenne> (raw)
In-Reply-To: <xmqqa6ez60l8.fsf@gitster.g>
On Thursday, 10 February 2022 01:12:51 CET Junio C Hamano wrote:
> * bs/forbid-i18n-of-protocol-token-in-fetch-pack (2021-12-22) 2 commits
> - fixup! fetch-pack: parameterize message containing 'ready' keyword
> - fetch-pack: parameterize message containing 'ready' keyword
>
> L10n support for a few error messages.
>
> Expecting an ack for fixup.
> source: <20211222075805.19027-1-bagasdotme@gmail.com>
>
Looks good to me.
Jean-Noël
next prev parent reply other threads:[~2022-02-11 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 0:12 What's cooking in git.git (Feb 2022, #02; Wed, 9) Junio C Hamano
2022-02-11 13:40 ` ds/sparse-checkout-requires-per-worktree-config (was Re: What's cooking in git.git (Feb 2022, #02; Wed, 9)) Derrick Stolee
2022-02-11 16:51 ` Junio C Hamano
2022-02-15 22:40 ` Eric Sunshine
2022-02-16 1:55 ` Junio C Hamano
2022-02-11 21:01 ` Jean-Noël AVILA [this message]
2022-02-11 22:38 ` What's cooking in git.git (Feb 2022, #02; Wed, 9) Junio C Hamano
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=1886649.yonrKIyjYj@cayenne \
--to=jn.avila@free.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.