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

Re: How to localize "git push"?

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Nov 27, 2025, 23:05 UTC
Message-ID
<aSjZKl17Vz4fMXxu@fruit.crustytoothpaste.net>
In-Reply-To
<f2cb6da7c17e8de829c3e4cb066684e2@softwolves.pp.se>
On 2025-11-26 at 07:50:15, Peter Krefting wrote:
> Hi!
Hi,
Show 14 quoted lines
> Re: https://fosstodon.org/@McPringle/115611195011002487
> 
> The message shown when running "git push" without any changes queued is
> always shown in English, whereas the corresponding message in "git pull" is
> properly localized.
> 
> I looked at the sources, and the string "Everything up-to-date\n" is
> included in both builtin/send-pack.c and transport.c, with both instances
> annotated with a comment "stable plumbing output; do not modify or
> localize".
> 
> How do we fix that? Having the message show in English from "git push" is
> confusing. What is the corresponding plumbing command that needs to have it
> machine-readable, so that we can fork that to fix "git push"?

There isn't any tooling in Git that requires that particular message but it's rather that other software outside of Git may depend on that output.

It should be noted that "Everything up-to-date" should actually be "Everything up to date", since it's an abbreviated form of "everything is up to date" and for most compound adjectives, we only hyphenate them in English before the noun they modify. However, because there was supposedly existing software that expected that output, we chose not to modify those messages at the time that cleanup went in. I am, however, unable to find any such software that expects that string on GitHub with a quick search.

Personally, I'm fine with modifying that message unless something like a `--plumbing` argument is given (or just letting people set `LC_ALL=C.UTF-8` if they want fixed output), but other people may not be.

I will say that we changed the following message sometime back for localization (to uppercase the N in "Needed") and it broke things at my last company, but we also easily fixed it and I'm pleased that it's now localized:

---- % git rev-parse --verify nonexistent fatal: Needed a single revision % LC_ALL=es_MX.UTF-8 git rev-parse --verify nonexistent fatal: Se necesitó una revisión singular % LC_ALL=fr_CA.UTF-8 git rev-parse --verify nonexistent fatal : Une seule révision attendue ----

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Peter Krefting
Message 2 of 2 in “How to localize "git push"?”
  1. Peter KreftingNov 26, 2025
  2. brian m. carlsonNov 27, 2025

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.