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
Taylor Blau <me@ttaylorr.com>
Date
Apr 17, 2019, 05:42 UTC
Message-ID
<20190417054250.GA98165@Taylors-MBP.hsd1.wa.comcast.net>
In-Reply-To
<xmqq7ebtkx7p.fsf@gitster-ct.c.googlers.com>
On Wed, Apr 17, 2019 at 02:38:34PM +0900, Junio C Hamano wrote:
Show 23 quoted lines
> Taylor Blau <me@ttaylorr.com> writes:
>
> > Hi Junio,
> >
> > On Tue, Apr 16, 2019 at 10:19:45PM +0900, Junio C Hamano wrote:
> >> * tb/unexpected (2019-04-10) 7 commits
> >> ...
> >>  Code tightening against a "wrong" object appearing where an object
> >>  of a different type is expected, instead of blindly assuming that
> >>  the connection between objects are correctly made.
> >
> > I sent a re-roll of this series in [1], which should be ready for
> > 'next' if you feel comfortable queueing it.
> >
> > [1]: https://public-inbox.org/git/cover.1554861974.git.me@ttaylorr.com/
>
> 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.
> Do you mean you have even newer ones?
No, those are the latest.
> Thanks.
>

Thanks, Taylor

Previous: Junio C HamanoNext: Junio C Hamano
Message 18 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.