git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2021, #06; Sat, 30)
Date: Tue, 2 Feb 2021 16:54:56 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2102021652350.54@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqy2g8mubh.fsf@gitster.c.googlers.com>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

Hi Junio,

On Sun, 31 Jan 2021, Junio C Hamano wrote:

> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
> > On Sun, Jan 31 2021, Junio C Hamano wrote:
> >
> >
> >> * ab/detox-gettext-tests (2021-01-21) 3 commits
> >>  - tests: remove uses of GIT_TEST_GETTEXT_POISON=false
> >>  - tests: remove support for GIT_TEST_GETTEXT_POISON
> >>  - ci: remove GETTEXT_POISON jobs
> >>
> >>  Get rid of "GETTEXT_POISON" support altogether, which may or may
> >>  not be controversial.
> >
> > I'm waiting on SZEDER'S feedback on [1], ditto the last What's
> > Cooking[2]. Also as noted in [2] the "do we keep GETTEXT_POISON at all"
> > question.
> >
> > How about we just remove it and see if people who love it will come out
> > of the woodworks, the patches aren't going to be hard to revert...
>
> Yeah, why not ;-)

I'll give you a reason. We're not really strong on the inclusion front,
and translations are one thing that we actually do right on that end.
Removing even the scant testing of translated messages that we do have
strikes me as the opposite of improving the situation.

Sadly, I won't have the time to pursue my GETTEXT_POISON effort further,
at least not in the short run, and y'all seem to be bent on making that
effort futile anyway.

So yeah, why not ;-)

Ciao,
Dscho

  reply	other threads:[~2021-02-02 16:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  0:00 What's cooking in git.git (Jan 2021, #06; Sat, 30) Junio C Hamano
2021-01-31  1:42 ` Taylor Blau
2021-01-31 20:50   ` Junio C Hamano
2021-01-31 17:21 ` SZEDER Gábor
2021-01-31 20:52   ` Junio C Hamano
2021-01-31 20:11 ` Derrick Stolee
2021-01-31 20:53   ` Junio C Hamano
2021-02-01  0:27 ` Ævar Arnfjörð Bjarmason
2021-02-01  1:48   ` Junio C Hamano
2021-02-02 15:54     ` Johannes Schindelin [this message]
2021-02-02 20:18       ` Junio C Hamano
2021-02-01 15:51 ` Charvi Mendiratta
2021-02-01 19:48   ` Junio C Hamano
2021-02-02 15:28     ` Charvi Mendiratta
2021-02-03  1:08 ` Đoàn Trần Công Danh
2021-02-03  1:22   ` Junio C Hamano
2021-02-03 22:00     ` Miriam R.
2021-02-04  1:38       ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.2102021652350.54@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).