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

Re: What's cooking (interim report)

From
Jeff King <peff@peff.net>
Date
Aug 4, 2016, 02:46 UTC
Message-ID
<20160804024645.vtjf5jwlz6pfz3lr@sigill.intra.peff.net>
In-Reply-To
<xmqqd1lp78r7.fsf@gitster.mtv.corp.google.com>
On Wed, Aug 03, 2016 at 04:06:20PM -0700, Junio C Hamano wrote:
Show 8 quoted lines
> * jk/parseopt-string-list (2016-08-03) 1 commit
>  - blame: drop strdup of string literal
> 
>  A recent API change to parse_opt_string_list() introduced a small
>  unintended memory leak in the command line parsing of "git blame",
>  which has been plugged.
> 
>  Will merge to 'next'.

Actually, the leak was always there. It's just that parse_opt_string_list used to leak _too_, and it was fixed, but this case left behind.

Not that it matters too much. I doubt this one is exciting enough to make it into the release notes. :)

Show 7 quoted lines
> * jk/pack-objects-optim-mru (2016-07-29) 1 commit
>  - pack-objects: use mru list when iterating over packs
>  (this branch uses jk/pack-objects-optim.)
> 
>  This is still questionable in that it can attempt to create a cycle
>  in delta-chain, only to be stopped by the last-ditch recovery logic
>  in there.

I've been doing some thinking and experimenting on this. I'll try to write up the current status tonight.

-Peff
Previous: Stefan Beller
Message 3 of 3 in “What's cooking (interim report)”
  1. Junio C HamanoAug 3, 2016
  2. Stefan BellerAug 3, 2016
  3. Jeff KingAug 4, 2016

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.