treewide: prefer lockfiles on the stack
commit837e34eba47f209a38fc9ab458bd103fd7515325
authorMartin Ågren <martin.agren@gmail.com>
Thu, 5 Oct 2017 20:32:04 +0000 (5 22:32 +0200)
committerJunio C Hamano <gitster@pobox.com>
Fri, 6 Oct 2017 01:07:17 +0000 (6 10:07 +0900)
treeab91a9de784eec03c56b431b51dd4649270cfd9c
parentf132a127eebb8f1b14b87fc317ca68278fceb2e8
treewide: prefer lockfiles on the stack

There is no longer any need to allocate and leak a `struct lock_file`.
The previous patch addressed an instance where we needed a minor tweak
alongside the trivial changes.

Deal with the remaining instances where we allocate and leak a struct
within a single function. Change them to have the `struct lock_file` on
the stack instead.

These instances were identified by running `git grep "^\s*struct
lock_file\s*\*"`.

Signed-off-by: Martin Ågren <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/am.c
builtin/checkout.c
builtin/clone.c
builtin/diff.c
config.c
merge-recursive.c
merge.c
wt-status.c