From: Chris Mason Date: Thu, 28 Apr 2005 17:05:21 GMT Subject: Re: Finding file revisions Message-ID: <200504281305.23063.mason@suse.com> In-Reply-To: On Thursday 28 April 2005 12:08, Daniel Barkalow wrote: > On Wed, 27 Apr 2005, Chris Mason wrote: > > I haven't seen a tool yet to find which changeset modified a given file, > > so I whipped up something. The basic idea is to: > > What is the answer supposed to be in the presence of merges? It seems like > you shouldn't report the merge that brought in the change, but rather > (assuming it's available) the changeset that originally made it. Based on comments from Linus I did make it a little more merge aware. But since my tool was just to tide me over until someone fixed things in gui form, I didn't want to kill off too many brain cells coding it. It sounds as though David's script is already has more merge brains then mine, and the git web stuff is pretty slick. So it seems I didn't look hard enough before... -chris