git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
	"Jeff Hostetler" <jeffhostetler@github.com>,
	"Alexander Shopov" <ash@kambanaria.org>,
	"Git List" <git@vger.kernel.org>,
	jmas@softcatala.org, alexhenrie24@gmail.com,
	ralf.thielow@gmail.com, matthias.ruester@gmail.com,
	phillip.szelat@gmail.com, vyruss@hellug.gr,
	christopher.diaz.riv@gmail.com, jn.avila@free.fr,
	flashcode@flashtux.org, bagasdotme@gmail.com,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	alessandro.menti@alessandromenti.it, elongbug@gmail.com,
	cwryu@debian.org, uneedsihyeon@gmail.com, arek_koz@o2.pl,
	dacs.git@brilhante.top, "insolor@gmail.com" <insolor@gmail.com>,
	peter@softwolves.pp.se, bitigchi@me.com, ark@cho.red,
	kate@kgthreads.com, "vnwildman@gmail.com" <vnwildman@gmail.com>,
	pclouds@gmail.com, "dyroneteng@gmail.com" <dyroneteng@gmail.com>,
	"oldsharp@gmail.com" <oldsharp@gmail.com>,
	"lilydjwg@gmail.com" <lilydjwg@gmail.com>,
	"pan93412@gmail.com" <pan93412@gmail.com>,
	"franklin@goodhorse.idv.tw" <franklin@goodhorse.idv.tw>
Subject: Re: Is there any interest in localizing term delimiters in git messages?
Date: Thu, 19 Oct 2023 21:47:47 +0200	[thread overview]
Message-ID: <20231019194747.GC25301@tb-raspi4> (raw)
In-Reply-To: <xmqqcyxaxzxw.fsf@gitster.g>

On Thu, Oct 19, 2023 at 10:52:11AM -0700, Junio C Hamano wrote:

>
> Also some of them might better be a BUG(), instead of die(_()).
>
> >  * crlf_action in convert.c:
> >
> >     warning(_("illegal crlf_action %d"), (int)crlf_action);
>
> [jch: cc'ed Torsten for area expertise].
>
> For example, can convert.c::output_eol() be called with an illegal
> crlf_action that is not covered by the switch() statement due to
> data error, not a programming error?  From my quick scan, it looks
> like that the error should never happen no matter what end-user
> mistakes (e.g., misspelt attribute and configuration variable names
> in their files) are fed to convert_attrs(), and can come only from a
> bug in that function (e.g., long and convoluted if/else cascade fails
> to assign any value to ca->crlf_action and leaves an undefined and
> "illegal" value there).

The switch case covers all 8 values of "enum crlf_action",
and removing these 2 lines
 -	warning("Illegal crlf_action %d\n", (int)crlf_action);
 -	return core_eol;
does still compile without a compiler warning.
So yes, a BUG is more appropriate here.
I hopefully find some time to send a patch the next days.

>
> Thanks.
>

  parent reply	other threads:[~2023-10-19 19:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 21:09 Is there any interest in localizing term delimiters in git messages? Alexander Shopov
2023-10-17 21:49 ` Junio C Hamano
2023-10-18  2:01   ` Jiang Xin
2023-10-18  2:47     ` Junio C Hamano
2023-10-18  3:08       ` [PATCH] commit: do not use cryptic "new_index" in end-user facing messages Junio C Hamano
2023-10-19  5:08       ` Is there any interest in localizing term delimiters in git messages? Jiang Xin
2023-10-19 17:52         ` Junio C Hamano
2023-10-19 18:07           ` Jeff Hostetler
2023-10-19 19:18             ` Junio C Hamano
2023-10-19 19:47           ` Torsten Bögershausen [this message]
2023-10-19 20:16             ` Junio C Hamano
2023-10-21  9:30 ` Peter Krefting

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=20231019194747.GC25301@tb-raspi4 \
    --to=tboegi@web.de \
    --cc=alessandro.menti@alessandromenti.it \
    --cc=alexhenrie24@gmail.com \
    --cc=arek_koz@o2.pl \
    --cc=ark@cho.red \
    --cc=ash@kambanaria.org \
    --cc=avarab@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=bitigchi@me.com \
    --cc=christopher.diaz.riv@gmail.com \
    --cc=cwryu@debian.org \
    --cc=dacs.git@brilhante.top \
    --cc=dyroneteng@gmail.com \
    --cc=elongbug@gmail.com \
    --cc=flashcode@flashtux.org \
    --cc=franklin@goodhorse.idv.tw \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=insolor@gmail.com \
    --cc=jeffhostetler@github.com \
    --cc=jmas@softcatala.org \
    --cc=jn.avila@free.fr \
    --cc=kate@kgthreads.com \
    --cc=lilydjwg@gmail.com \
    --cc=matthias.ruester@gmail.com \
    --cc=oldsharp@gmail.com \
    --cc=pan93412@gmail.com \
    --cc=pclouds@gmail.com \
    --cc=peter@softwolves.pp.se \
    --cc=phillip.szelat@gmail.com \
    --cc=ralf.thielow@gmail.com \
    --cc=uneedsihyeon@gmail.com \
    --cc=vnwildman@gmail.com \
    --cc=vyruss@hellug.gr \
    --cc=worldhello.net@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 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).