From: Kay Sievers Date: Thu, 28 Apr 2005 16:34:59 GMT Subject: Re: Finding file revisions Message-ID: <1114706099.4212.25.camel@localhost.localdomain> In-Reply-To: <200504280745.05505.mason@suse.com> On Thu, 2005-04-28 at 07:45 -0400, Chris Mason wrote: > On Wednesday 27 April 2005 18:19, Linus Torvalds wrote: > > On Wed, 27 Apr 2005, Chris Mason wrote: > > > So, new prog attached. New usage: > > > > > > file-changes [-c commit_id] [-s commit_id] file ... > > > > > > -c is the commit where you want to start searching > > > -s is the commit where you want to stop searching > > > > Your script will do some funky stuff, because you incorrectly think that > > the rev-list is sorted linearly. It's not. It's sorted in a rough > > chronological order, but you really can't do the "last" vs "cur" thing > > that you do, because two commits after each other in the rev-list listing > > may well be from two totally different branches, so when you compare one > > tree against the other, you're really doing something pretty nonsensical. > > One more rev that should work as you suggested Here's the example output > from a cogito changeset with merges. I print the diff-tree lines once for each > matching parent and then print the commit once. It's very primitive, but > hopefully some day someone will make a gui with happy clicky buttons > for changesets and filerevs. Not really happy clicky, but ... :) Look at the (history) link: http://ehlo.org/~kay/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=fb3b4ebc0be618dbcc2326482a83c920d51af7de Kay