Re: Kernel headers git tree

> 
> > But that thing is doubly strange, because it uses "." as a path specifier. 
> > If this is done in the top-most directory, that should mean "all changes", 
> > which in turn means that the whole thing should be equivalent to
> > 
> > 	git rev-parse "$1^0"
> > 
> > since all commits should make _some_ change, and thus the first revision 
> > in the list should always be the top commit - the one you passed in as an 
> > argument.
> 
> In this case, I really do have commits in the intermediate tree which
> don't actually change anything, and I want to filter them out -- I
> couldn't see a simple way to do it all in one pass.