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

Re: What's cooking in git.git (Aug 2025, #01; Sun, 3)

From
Ben Knoble <ben.knoble@gmail.com>
Date
Aug 5, 2025, 19:18 UTC
Message-ID
<7923AA49-A1E9-4E56-9397-0443481B97B8@gmail.com>
In-Reply-To
<xmqqectpziz9.fsf@gitster.g>
Show 17 quoted lines
> Le 5 août 2025 à 15:06, Junio C Hamano <gitster@pobox.com> a écrit :
> 
> "D. Ben Knoble" <ben.knoble@gmail.com> writes:
> 
>> With apologies for the mail noise, but I can't seem to reproduce any
>> failures here on 371c45b569 (Merge branch 'dk/help-all' into seen,
>> 2025-08-04), which is the latest seen I can find.
> 
> When I report a public CI failure, I'd try to give an exact URL, but
> otherwise the failure would have been seen in my local environment,
> and because I tend to refrain from pushing out a know-to-be-broken
> tree, it is unsurprising if 371c45b569 did not fail.
> 
> That commit does not have lo/repo-info, I suspect.  I didn't know
> exactly which topic was causing, but the error was observed when
> "repo --help-all" was given, so perhaps some interactions between
> these two topics.
I did also try a merge between 371c… and lo/repo-info with similar success. :/
If you happen to find such a faulty tree again, would you consider publishing a broken branch I can fetch?
Previous: Junio C HamanoNext: Lucas Seiki Oshiro
Message 18 of 20 in “What's cooking in git.git (Aug 2025, #01; Sun, 3)”
  1. Junio C HamanoAug 4, 2025
  2. Patrick SteinhardtAug 4, 2025
  3. Junio C HamanoAug 4, 2025
  4. Patrick SteinhardtAug 4, 2025
  5. Jeff KingAug 4, 2025
  6. Junio C HamanoAug 5, 2025
  7. Jeff KingAug 5, 2025
  8. Junio C HamanoAug 5, 2025
  9. Jeff KingAug 5, 2025
  10. Patrick SteinhardtAug 5, 2025
  11. Jeff KingAug 5, 2025
  12. Junio C HamanoAug 5, 2025
  13. D. Ben KnobleAug 5, 2025
  14. Junio C HamanoAug 5, 2025
  15. D. Ben KnobleAug 5, 2025
  16. D. Ben KnobleAug 5, 2025
  17. Junio C HamanoAug 5, 2025
  18. Ben KnobleAug 5, 2025
  19. Lucas Seiki OshiroAug 6, 2025
  20. Junio C HamanoAug 6, 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.