Re: leaky cherry-pick

Pete Wyckoff [off-list ref] writes:

I've got a big tree, and rebased 200 commits today using
cherry-pick.  It ran out of memory....

    valgrind --log-file=/tmp/vg.out --leak-check=full \
    /home/pw/src/git/git cherry-pick 8d535b6^..2cf53a0

The cherry-pick and revert machinery was written to be single-shot and the
multi-pick feature was bolted on to it later; I am not so surprised if
nobody carefully looked at the memory usage when that happened.

Ram?