Here comes another bunch of memory leaks fixed. patches 1-4 are safe bets, but 5 and 6 are not so. In patch 5 I wonder if we need to fix more aggressively and in patch 6 I just know there is a leak but I have no idea how to actually fix it. The patches are apply-able to origin/master. Version 2 has no changes in code but in recipients. CC'ing parties who may be qualified to review the patches. Stefan Beller (6): shallow: fix a memleak line-log.c: fix a memleak line-log.c: fix a memleak wt-status.c: fix a memleak pack-bitmap: fix a memleak WIP/RFC/entry.c: fix a memleak entry.c | 4 +++- line-log.c | 4 ++++ pack-bitmap.c | 27 ++++++++++++++++++--------- shallow.c | 4 ++-- wt-status.c | 2 ++ 5 files changed, 29 insertions(+), 12 deletions(-) -- 2.3.0.81.gc37f363 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html