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

Re: [PATCH] push: improve consistency of output when "up to date"

From
BKBenji Kay <okaybenji@gmail.com>
Date
Jan 12, 2024, 00:55 UTC
Message-ID
<CADavbxdexJ-nzbiicLF7SOJsELKW5J5Zox5MFGdWDHhcE=85VQ@mail.gmail.com>
In-Reply-To
<CADavbxcFXpP5EQZ=UEMZt+6KKVtCsTMbgQDHEo0uinm0YfRbZA@mail.gmail.com>

If it's important these messages are not changed (under the presumption some programs may make decisions based on the output), perhaps a test should be written to ensure the output is as expected.

Previous: Dragan Simic
Message 11 of 11 in “push: improve consistency of output when "up to date"”
  1. push: improve consistency of output when "up to date"Benji Kay via GitGitGadget, Jan 11, 2024
  2. Eric SunshineJan 11, 2024
  3. Junio C HamanoJan 11, 2024
  4. Eric SunshineJan 12, 2024
  5. messages: mark some strings with "up-to-date" not to touchEric Sunshine, Jan 12, 2024
  6. Junio C HamanoJan 12, 2024
  7. Patrick SteinhardtJan 15, 2024
  8. Taylor BlauJan 11, 2024
  9. Eric SunshineJan 11, 2024
  10. Dragan SimicJan 17, 2024
  11. Benji KayJan 12, 2024

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.