From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 09 Jan 2012 23:19:54 GMT
Subject: Re: leaky cherry-pick
Message-ID: <7vk450cvl1.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120109223737.GA1589@padd.com>

Pete Wyckoff <pw@padd.com> 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?