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

Re: Git CLI

From
Denton Liu <liu.denton@gmail.com>
Date
Nov 22, 2019, 18:04 UTC
Message-ID
<20191122180433.GA57478@generichostname>
In-Reply-To
<3AD06998-1729-46C2-8B60-BD405C365656@me.com>
Hi Craig,
Thanks for the report.
On Fri, Nov 22, 2019 at 08:12:48AM -0500, Craig H Maynard wrote:
Show 8 quoted lines
> Just noticed this:
> 
> $ git pull
> Already up to date.
> $ git push
> Everything up-to-date
> 
> The two messages covey the same information but use different punctuation and hyphenation. While not terribly important, this quirky inconsistency doesn't inspire confidence.

Unfortunately, this has been caught before but remains for legacy reasons.

According to 7560f547e6 (treewide: correct several "up-to-date" to "up to date", 2017-08-23), it explicitly mentions in the commit message, "Don't change plumbing (specifically send-pack.c, but transport.c (git push) also has the same string)."

So as a result, we can't change the `git push` string to match. I don't think it would make too much sense to change the `git pull` string to match either since that would intentionally introduce the "up-to-date" error that the above commit fixed.

Thanks,
Denton
Show 10 quoted lines
> 
> My environment:
> 
> git version 2.24.0
> hub version 2.13.0
> 
> --
> Craig H Maynard
> Rhode Island, USA
>
Previous: Craig H Maynard
Message 2 of 2 in “Git CLI”
  1. Craig H MaynardNov 22, 2019
  2. Denton LiuNov 22, 2019

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.