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

Re: What's cooking in git.git (Oct 2023, #01; Mon, 2)

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 4, 2023, 16:28 UTC
Message-ID
<xmqq5y3ms67j.fsf@gitster.g>
In-Reply-To
<875y3n4207.fsf@email.froward.int.ebiederm.org>
"Eric W. Biederman" <ebiederm@xmission.com> writes:
Show 5 quoted lines
> I pushed v2 out precisely because it contains fixes that should have
> fixed all of the CI breakages.
>
> I am not really familiar with github but looking at the recent CI runs
> it appears since v2 landed the seen branch has been building cleanly.

https://github.com/git/git/actions/runs/6398848314 shows the CI run with seen at 7052c9b and it seems it does have the eb/hash-transition topic in it.

> I just don't want people to avoid reviewing it because it is that huge
> patchset that causes problems in seen.
Certainly.

I have seen people review patches that do not even compile, though, so "problems in seen" may not be that much of an issue, compared to how intimidating the large series looks like.

Thanks.
Previous: Eric W. Biederman
Message 12 of 12 in “What's cooking in git.git (Oct 2023, #01; Mon, 2)”
  1. Junio C HamanoOct 3, 2023
  2. Sergey OrganovOct 3, 2023
  3. Junio C HamanoOct 3, 2023
  4. Sergey OrganovOct 3, 2023
  5. Junio C HamanoOct 4, 2023
  6. Sergey OrganovOct 4, 2023
  7. Junio C HamanoOct 5, 2023
  8. Sergey OrganovOct 5, 2023
  9. Junio C HamanoOct 5, 2023
  10. Sergey OrganovOct 6, 2023
  11. Eric W. BiedermanOct 4, 2023
  12. Junio C HamanoOct 4, 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.