| commit | 4c520cefc90b10566fcc8a0b006287494a7770e1 | |
| author | John Keeping <john@keeping.me.uk> | |
| Sun, 13 Feb 2022 15:34:50 +0000 (13 15:34 +0000) | ||
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | |
| Mon, 19 Dec 2022 15:13:58 +0000 (19 16:13 +0100) | ||
| tree | 92552dae5b62a8aba4e6ad4002716ec189dd3036 | treesnapshot (tar.gz zip) |
| parent | d071f28cfa9a49f3aa6355b17e9d9fa7224ff49f | commitdiff |
global: use release_commit_memory()
Instead of calling two separate Git functions to free memory associated
with a commit object, use Git's wrapper which does this. This also
counts as a potential future bug fix since release_commit_memory() also
resets the parsed state of the commit, meaning any attempt to use it in
the future will correctly fill out the fields again.
release_commit_memory() does not set parents to zero, so keep that for
additional safety in case CGit checks this without calling
parse_commit() again.
Signed-off-by: John Keeping <john@keeping.me.uk>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Instead of calling two separate Git functions to free memory associated
with a commit object, use Git's wrapper which does this. This also
counts as a potential future bug fix since release_commit_memory() also
resets the parsed state of the commit, meaning any attempt to use it in
the future will correctly fill out the fields again.
release_commit_memory() does not set parents to zero, so keep that for
additional safety in case CGit checks this without calling
parse_commit() again.
Signed-off-by: John Keeping <john@keeping.me.uk>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
| ui-atom.c | diffblobblamehistory | |
| ui-log.c | diffblobblamehistory | |
| ui-stats.c | diffblobblamehistory |