All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrick Stolee <derrickstolee@github.com>
To: "Junio C Hamano" <gitster@pobox.com>,
	git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: ab/plug-random-leaks (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3))
Date: Fri, 4 Mar 2022 08:25:56 -0500	[thread overview]
Message-ID: <5f8740bd-c0b7-a8e1-4d73-b79b40cc02e9@github.com> (raw)
In-Reply-To: <xmqqv8wu2vag.fsf@gitster.g>

On 3/3/2022 11:31 PM, Junio C Hamano wrote:

> * ab/plug-random-leaks (2022-03-02) 14 commits
>  - repository.c: free the "path cache" in repo_clear()
>  - range-diff: plug memory leak in read_patches()
>  - range-diff: plug memory leak in common invocation
>  - lockfile API users: simplify and don't leak "path"
>  - commit-graph: stop fill_oids_from_packs() progress on error and free()
>  - commit-graph: fix memory leak in misused string_list API
>  - submodule--helper: fix trivial leak in module_add()
>  - transport: stop needlessly copying bundle header references
>  - bundle: call strvec_clear() on allocated strvec
>  - remote-curl.c: free memory in cmd_main()
>  - urlmatch.c: add and use a *_release() function
>  - diff.c: free "buf" in diff_words_flush()
>  - merge-base: free() allocated "struct commit **" list
>  - index-pack: fix memory leaks
> 
>  Plug random memory leaks.
> 
>  Will merge to 'next'.
>  source: <cover-00.14-00000000000-20220302T170718Z-avarab@gmail.com>

This series needs a re-roll before it gets merged. There is
a correctness issue in this patch:

>  - transport: stop needlessly copying bundle header references

Thanks,
-Stolee

  reply	other threads:[~2022-03-04 13:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04  4:31 What's cooking in git.git (Mar 2022, #01; Thu, 3) Junio C Hamano
2022-03-04 13:25 ` Derrick Stolee [this message]
2022-03-04 18:33   ` ab/plug-random-leaks (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3)) Ævar Arnfjörð Bjarmason
2022-03-17 12:46     ` [PATCH] tests: test show --word-diff --color-moved Michael J Gruber
2022-03-17 14:55       ` [PATCH v2 0/2] diff.c: fix a recent memory leak regression Ævar Arnfjörð Bjarmason
2022-03-17 14:55         ` [PATCH v2 1/2] tests: demonstrate "show --word-diff --color-moved" regression Ævar Arnfjörð Bjarmason
2022-03-17 15:54           ` Junio C Hamano
2022-03-17 14:55         ` [PATCH v2 2/2] diff.c: fix a double-free regression in a18d66cefb Ævar Arnfjörð Bjarmason
2022-03-04 15:35 ` tb/cruft-packs (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3)) Derrick Stolee
2022-03-07 18:06   ` Jonathan Nieder
2022-03-07 18:18     ` Taylor Blau
2022-03-07 18:32       ` Derrick Stolee
2022-03-07 20:18         ` Jonathan Nieder
2022-03-07 20:51           ` Derrick Stolee
2022-03-07 21:34             ` Junio C Hamano
2022-03-08  0:52               ` Taylor Blau
2022-03-08  0:25       ` Junio C Hamano
2022-03-08  0:49         ` Taylor Blau
2022-03-05 14:25 ` jc/stash-drop (was: " Ævar Arnfjörð Bjarmason
2022-03-07 18:22   ` jc/stash-drop Junio C Hamano
2022-03-07 13:49 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Mar 2022, #01; Thu, 3)) Derrick Stolee
2022-03-07 17:18   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f8740bd-c0b7-a8e1-4d73-b79b40cc02e9@github.com \
    --to=derrickstolee@github.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.