From: Junio C Hamano Date: Tue, 16 May 2006 06:13:12 GMT Subject: Re: [PATCH] Update the documentation for git-merge-base Message-ID: <7vhd3qebuv.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <20060516055815.GA4572@c165.ib.student.liu.se> Fredrik Kuivinen writes: > Is the code guaranteed to return a least common ancestor? If that is > the case we should probably mention it in the documentation. Unfortunately, no, if you mean by "least common" closest to the tips. See the big illustration at the top of the source for how you can construct pathological case to defeat an attempt to guarantee such. --all guarantees that the output contains all interesting ones, but does not guarantee the output has no suboptimal merge bases.