From: Junio C Hamano Date: Mon, 22 Mar 2010 07:41:20 GMT Subject: Re: GSoC draft proposal: Line-level history browser Message-ID: <7v7hp4n6qn.fsf@alter.siamese.dyndns.org> In-Reply-To: <41f08ee11003220031p6fda651eycff2641df10864da@mail.gmail.com> Bo Yang writes: >> When you want to know where the first few lines of Makefile >> came from, and if blame says the first line came from 2731d048, that >> really means that between the revision you started digging from and the >> found revision, there is no commit that touched that particular line, but >> equally importantly, that before that found revision, there wasn't a >> corresponding line in that file---blame stopped exactly because there is >> nobody before that found revision that the line can be blamed on. > ... > Yes, this is not satisfying. But as I understand, the line level > history browser will do more than just this. It will not stop on 'step > 4', it can follow the change history recursively and deeply, to find > more. I am actually questioning the existence of "recursively and deeply to find more"; the reason blame stopped at a particular commit is exactly because there is no more---otherwise it wouldn't have stopped there but kept digging deeper. That is what I meant in the message you are responding to, quoted at the top of this message.