Re: potential improvement to 'git log' with a range
- From
- Santi Béjar <santi@agolina.net>
- Date
- Apr 9, 2010, 23:33 UTC
- Message-ID
- <h2gadf1fd3d1004091633qe27d49f0m2ecb461e56f405b1@mail.gmail.com>
- In-Reply-To
- <w2j3abd05a91004091624mb2836ff4v118a1ae9ac5ca6e7@mail.gmail.com>
On Sat, Apr 10, 2010 at 1:24 AM, Aghiles <aghilesk@gmail.com> wrote:
Show 10 quoted lines
> If I type: > > git log FETCH_HEAD~4..HEAD > > I get something. But if I type: > > git log HEAD..FETCH_HEAD~4 > > I get nothing. Is there a good reason for that ? >
Yes.
$ git log -h usage: git log [<options>] [<since>..<until>] [[--] <path>...]
So <since> and <until> are not equivalent. It list commits in <until> but not in <since>.
In your case HEAD has commits not in FETCH_HEAD~4 (your first command) while FETCH_HEAD~4 does not have commits not in HEAD. So HEAD is a descendent of FETCH_HEAD~4.
Hope I didn't misunderstood your question.
HTH, Santi