Re: [PATCH] object-name: explain why <ref>~N fails in a shallow clone

It is obvious that users would see such a message when they say

    $ git show HEAD~20
    $ git log HEAD~20..HEAD

but would they see the same when

    $ git log -20 HEAD
    $ git log --since=2.months HEAD

and internally HEAD~20 fails to resolve?  Should they see the same
hint?

But I think the 'log -20' doesn't even give an error, so where would
we show that message?


Harald