threads / discuss / 15234

git-whatchanged -<n>

Subject: git-whatchanged -<n>

## tl;dr

One message between Aug 28, 2008 and Aug 28, 2008.

replies: 0people: 1as markdown or json

Karl Chen· Aug 28, 2008, 00:07 UTC · lore

Is this a bug in git-whatchanged, or at least an insufficiently documented feature?

cd git
git whatchanged 837a156197e7~20..837a156197e7 -1 
    [nothing]
git whatchanged 837a156197e7~20..837a156197e7 -3
    [1 commit]
git whatchanged 837a156197e7~20..837a156197e7 -1 -m
    [1(?) commit]

It appears that without -m, merges are filtered after commits are counted.

← back to recent threads