From: "Martin Ågren" <martin.agren@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 0/2] Re: reduce_heads: fix memory leaks
Date: Sun, 5 Nov 2017 21:26:29 +0100 [thread overview]
Message-ID: <cover.1509908607.git.martin.agren@gmail.com> (raw)
In-Reply-To: <CAN0heSpgUBy4a6iok4MoDqJ__hZtrXvfApcxjHuS0vOBKSuShg@mail.gmail.com>
Since v1 [1], I've added a preparatory patch to UNLEAK some variables.
That sets the stage slightly better for patch 2.
Junio, you placed v1 on maint. Because UNLEAK is not in maint, this is
based on master and maint misses out on this v2. If you have any advice
for how I should (not) do series with UNLEAK in them, I'm all ears.
Martin
[1] https://public-inbox.org/git/20171101090326.8091-1-martin.agren@gmail.com/
Martin Ågren (2):
builtin/merge-base: UNLEAK commit lists
reduce_heads: fix memory leaks
commit.h | 18 +++++++++++++++++-
builtin/commit.c | 2 +-
builtin/fmt-merge-msg.c | 2 +-
builtin/merge-base.c | 40 +++++++++++++++++++++-------------------
builtin/merge.c | 1 +
builtin/pull.c | 5 ++++-
commit.c | 7 +++++++
7 files changed, 52 insertions(+), 23 deletions(-)
--
2.15.0.415.gac1375d7e
next prev parent reply other threads:[~2017-11-05 20:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 9:03 [PATCH] reduce_heads: fix memory leaks Martin Ågren
2017-11-02 3:11 ` Junio C Hamano
2017-11-02 10:45 ` Martin Ågren
2017-11-05 20:26 ` Martin Ågren [this message]
2017-11-05 20:26 ` [PATCH v2 1/2] builtin/merge-base: UNLEAK commit lists Martin Ågren
2017-11-06 1:03 ` Junio C Hamano
2017-11-06 11:05 ` Jeff King
2017-11-07 20:39 ` [PATCH v3 1/2] builtin/merge-base: free " Martin Ågren
2017-11-08 2:40 ` Junio C Hamano
2017-11-07 20:39 ` [PATCH v3 2/2] reduce_heads: fix memory leaks Martin Ågren
2017-11-05 20:26 ` [PATCH v2 " Martin Ågren
2017-11-06 1:12 ` [PATCH v2 0/2] " 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=cover.1509908607.git.martin.agren@gmail.com \
--to=martin.agren@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.