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

Re: [PATCH] unpack-trees: correctly compute result count

From
Derrick Stolee <stolee@gmail.com>
Date
Jan 10, 2020, 11:24 UTC
Message-ID
<d9a465bf-843b-2a8f-66c0-73fb706dbfc0@gmail.com>
In-Reply-To
<20200110103729.GA470836@coredump.intra.peff.net>
On 1/10/2020 5:37 AM, Jeff King wrote:
Show 12 quoted lines
> On Fri, Jan 10, 2020 at 01:59:30AM +0000, Derrick Stolee via GitGitGadget wrote:
>>
>>     As for making it into the release, I don't know. The change is small, it
>>     has a very limited scope, but this flaw is also not really hurting
>>     anything in a major way.
> 
> I could go either way.
> 
> This counts as something small and obvious enough that I'd consider
> slipping it in at the last minute if it were fixing a bad bug. But given
> how minor the bug is, being conservative makes sense to me, if only
> because it's good to exercise our release discipline muscles. :)
Perhaps this should be an example for future release windows.

Thanks, -Stolee

Previous: Jeff KingNext: Derrick Stolee
Message 3 of 5 in “unpack-trees: correctly compute result count”
  1. unpack-trees: correctly compute result countDerrick Stolee via GitGitGadget, Jan 10, 2020
  2. Jeff KingJan 10, 2020
  3. Derrick StoleeJan 10, 2020
  4. Derrick StoleeJan 10, 2020
  5. Junio C HamanoJan 10, 2020

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.