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

Re: What's cooking in git.git (Apr 2021, #05; Mon, 19)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 20, 2021, 23:51 UTC
Message-ID
<xmqqk0ow1plt.fsf@gitster.g>
In-Reply-To
<87mttt2hcu.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 12 quoted lines
> On Tue, Apr 20 2021, Junio C Hamano wrote:
>
> Comments on my outstanding serieses and related (you've indicated that
> this summary was helpful, so I'll keep doing it).
>
>> * ab/unexpected-object-type (2021-04-14) 11 commits
>> ...
> I've just re-rolled these three at:
>
>  * https://lore.kernel.org/git/cover-00.10-0000000000-20210420T124428Z-avarab@gmail.com
>  * https://lore.kernel.org/git/cover-00.10-0000000000-20210420T125415Z-avarab@gmail.com
>  * https://lore.kernel.org/git/cover-0.8-0000000000-20210420T133218Z-avarab@gmail.com

Unfortunately, I didn't get to these three. In the meantime, I'd expect you to try merging these three into 'seen' once it gets published today, and invite others who have topics not in 'next' but in 'seen' to also do so. By doing so, you'd see what interactions, if any, are expected with the other topics in-flight. I'd hope them to be minimal---the old ab/unexpected-object-type had only one "yes, that might be nice standalone if you are not working together with other people, but we didn't have to make this change and we would have saved having to do an evil merge to resolve this conflict if we didn't"---as the old topic is tenatively ejected, the evil merge is gone for now from 'seen', which is good ;-).

Anyway, without these three, but with the few topics that depends on updated test-lib-updates topioc, the integration of the topics in 'seen' for today's cycle has been smooth. The test-lib-updates still had the same few niggles in its early parts I pointed out in an earlier round, though. Among the topics from you, I'd think that one would be the highest priority, simply because many other topics are taken hostage to it. It matters to me a lot, as I'd be the one who ends up having to remember what depends on what else, and having to rebase them on top of each other. The sooner that topic solidifies, the better for other topics that depend on it.

Thanks.
Previous: brian m. carlsonNext: Jeff King
Message 8 of 10 in “What's cooking in git.git (Apr 2021, #05; Mon, 19)”
  1. Junio C HamanoApr 19, 2021
  2. Matheus Tavares BernardinoApr 20, 2021
  3. Ævar Arnfjörð BjarmasonApr 20, 2021
  4. Junio C HamanoApr 20, 2021
  5. brian m. carlsonApr 20, 2021
  6. Ævar Arnfjörð BjarmasonApr 21, 2021
  7. brian m. carlsonApr 21, 2021
  8. Junio C HamanoApr 20, 2021
  9. Jeff KingApr 23, 2021
  10. Jeff HostetlerApr 20, 2021

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.