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

Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 17, 2019, 06:14 UTC
Message-ID
<xmqqwojtjgzf.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190417054250.GA98165@Taylors-MBP.hsd1.wa.comcast.net>
Taylor Blau <me@ttaylorr.com> writes:
Show 21 quoted lines
>> That's this one
>>
>>     Date: Tue, 9 Apr 2019 19:13:06 -0700 (1 week, 3 hours, 23 minutes ago)
>>     Subject: [PATCH v2 0/7] harden unexpected object types checks
>>
>> which I think is what has been queued and what is listed in the
>> message you are responding to.
>
> Ah, perhaps you could clarify some confusion I have about the "What's
> Cooking" emails (or at least point me somewhere I could un-confuse
> myself).
>
> This topic is in the "Cooking" section with a "-" (which I recall means
> that it's in 'pu'), but there is no "Will merge to ..." line below it
> from you.
>
> That makes sense to me, but I'm not sure whether or not that means it's
> queued. Do you say that a topic is queued once it's on your pu, or once
> you have written "Will merge to..."?
>
> Thanks in advance for your clarification.

Hmph, I guess I shouldn't use the verb "queue" if it implies a lot more than there is to it. I create a topic branch out of a patch series on the list at some point in the iteration of a series and merge it to 'pu'; I can say "I queued the topic to 'pu'" after doing so. The verb to me does not mean anything more than that.

The fact that a topic is queued on 'pu' does not mean much. It can be taken as a sign "Gitster thought that it may become 'next' worthy material, either as-is or with further polishing and replacing." Once a topic gets discussed on list and it seems apparent that there is a concensus that supports it, I may mark the topic as "Will merge to 'next'" in the What's cooking report, but I may not realize that the list already reached such a concensus and may leave it unmarked in the report.

So "this has been battle tested in such and such environment" and/or "this round was reviwed by the thread here and they were supportive" etc. is a very appreciated response to the "what's cooking" report to help me merge the topic down to 'next'.

"I have sent a reroll at ..." I typically hear when I miss a rerolled version and what is listed is still from an old iteration, hence my "Eh, you are pointing at what I have queued" reaction.

Thanks.
Previous: Taylor BlauNext: Taylor Blau
Message 19 of 24 in “What's cooking in git.git (Apr 2019, #03; Tue, 16)”
  1. Junio C HamanoApr 16, 2019
  2. Ævar Arnfjörð BjarmasonApr 16, 2019
  3. Junio C HamanoApr 16, 2019
  4. Ævar Arnfjörð BjarmasonApr 17, 2019
  5. Junio C HamanoApr 18, 2019
  6. Duy NguyenApr 17, 2019
  7. Phillip WoodApr 17, 2019
  8. Ævar Arnfjörð BjarmasonApr 17, 2019
  9. Ben PeartApr 16, 2019
  10. Junio C HamanoApr 17, 2019
  11. Stalled ds/ branches (was What's cooking in git.git (Apr 2019, #03; Tue, 16))Derrick Stolee, Apr 16, 2019
  12. jt/clone-server-option (was What's cooking in git.git (Apr 2019, #03; Tue, 16))Jonathan Tan, Apr 16, 2019
  13. Junio C HamanoApr 17, 2019
  14. Jonathan TanApr 17, 2019
  15. Junio C HamanoApr 18, 2019
  16. Taylor BlauApr 17, 2019
  17. Junio C HamanoApr 17, 2019
  18. Taylor BlauApr 17, 2019
  19. Junio C HamanoApr 17, 2019
  20. Taylor BlauApr 18, 2019
  21. jc/format-patch-error-check, was Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)Johannes Schindelin, Apr 17, 2019
  22. Junio C HamanoApr 18, 2019
  23. ab/test-lib-pass-trace2-env, was Re: What's cooking in git.git (Apr 2019, #03; Tue, 16)Johannes Schindelin, Apr 17, 2019
  24. Denton LiuApr 18, 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.