On Thu, Apr 18, 2013 at 5:26 AM, John Keeping <j...@keeping.me.uk> wrote:
> On Thu, Apr 18, 2013 at 05:17:14AM -0500, Felipe Contreras wrote:
>> If I do these:
>> % git log --oneline -1 v18.104.22.168^..v22.214.171.124
>> % git log --oneline --reverse -1 v126.96.36.199^..v188.8.131.52
>> I expect to get a different output, and not both showing v184.108.40.206.
>> Wouldn't you agree?
> I expect to get the same output. This is probably because I consider
> --reverse to be an output filter. So I expect to show the commits
> "v220.127.116.11^..v18.104.22.168 -1" which selects a single commit and then show
> that in reverse order.
How about this:
% git log --oneline --reverse --max-count=1 v22.214.171.124^..v126.96.36.199
In this case --max-count is acting as "start from the first commit
before the tip", not as "output a maximum of one commit". Given that
the name is max-count, I expect it to be the later.
And if max-count doesn't select a maximum of n commits, then what does?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html