On Thu, 21 Jul 2005, Ryan Anderson wrote:
>
> Nevermind, I apparently wanted:
> git-whatchanged HEAD ^$LAST_RELEASED_COMMIT
Yes. And since git-whatchanged uses git-rev-parse, and can thus use the
extended git commit format, including ranges, you can literally write the
above as
Nevermind, I apparently wanted:
git-whatchanged HEAD ^$LAST_RELEASED_COMMIT
I'll see about writing up a description of the extended commit reference
scheme. Currently I can't find a description of it anywhere in the
source tree.
On Thu, Jul 21, 2005 at 02:31:43AM -0400, Ryan Anderson wro
I'll start by saying that, well, I'm pretty sure this patch is wrong.
I was trying to look at the changes between two commits, sanely, but
failed to find a tool or example in the tree that hinted at how to do
this.
After poking around at git-whatchanged trying to figure out what it is
trying to d
3 matches
Mail list logo
