git.99rst.org / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0748f41)
gitk: Clear array 'commitinfo' on reload
authorMarkus Hitter <redacted>
Mon, 7 Nov 2016 18:02:51 +0000 (19:02 +0100)
committerPaul Mackerras <redacted>
Mon, 12 Dec 2016 09:39:37 +0000 (20:39 +1100)
commit18ae912082736b4c2c596b2c5bdcf2e032a03467
treeb2b1023768339d6b7dcb03645f0e16d160bf3c76tree | snapshot
parent0748f41eb83194dbc310fe47b4948f611ac5b3a2commit | diff
gitk: Clear array 'commitinfo' on reload

After a reload we might have an entirely different set of commits,
so keeping all of them leaks memory. Remove them all because
re-creating them is not more expensive than testing wether they're
still valid. Lazy (re-)creation is already well established, so
a missing entry can't cause harm.

Signed-off-by: Markus Hitter <redacted>
Signed-off-by: Paul Mackerras <redacted>
gitk diff | blob | history
git clone https://git.99rst.org/PROJECT