git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Is there any interest in localizing term delimiters in git messages?

From
Torsten Bögershausen <tboegi@web.de>
Date
Oct 19, 2023, 19:47 UTC
Message-ID
<20231019194747.GC25301@tb-raspi4>
In-Reply-To
<xmqqcyxaxzxw.fsf@gitster.g>
On Thu, Oct 19, 2023 at 10:52:11AM -0700, Junio C Hamano wrote:
Show 18 quoted lines
>
> 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.
>
Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 12 in “Is there any interest in localizing term delimiters in git messages?”
  1. Alexander ShopovOct 17, 2023
  2. Junio C HamanoOct 17, 2023
  3. Jiang XinOct 18, 2023
  4. Junio C HamanoOct 18, 2023
  5. commit: do not use cryptic "new_index" in end-user facing messagesJunio C Hamano, Oct 18, 2023
  6. Jiang XinOct 19, 2023
  7. Junio C HamanoOct 19, 2023
  8. Jeff HostetlerOct 19, 2023
  9. Junio C HamanoOct 19, 2023
  10. Torsten BögershausenOct 19, 2023
  11. Junio C HamanoOct 19, 2023
  12. Peter KreftingOct 21, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.