From: "Santi Béjar" <santi@agolina.net>
To: Aghiles <aghilesk@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: potential improvement to 'git log' with a range
Date: Sat, 10 Apr 2010 01:33:01 +0200 [thread overview]
Message-ID: <h2gadf1fd3d1004091633qe27d49f0m2ecb461e56f405b1@mail.gmail.com> (raw)
In-Reply-To: <w2j3abd05a91004091624mb2836ff4v118a1ae9ac5ca6e7@mail.gmail.com>
On Sat, Apr 10, 2010 at 1:24 AM, Aghiles <aghilesk@gmail.com> wrote:
> 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
next prev parent reply other threads:[~2010-04-09 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 23:24 potential improvement to 'git log' with a range Aghiles
2010-04-09 23:33 ` Santi Béjar [this message]
2010-04-09 23:33 ` Sverre Rabbelier
2010-04-10 0:13 ` Aghiles
2010-04-10 0:16 ` Sverre Rabbelier
2010-04-10 1:20 ` Linus Torvalds
2010-04-11 20:31 ` Aghiles
2010-04-11 21:32 ` Jakub Narebski
2010-06-23 17:05 ` Martin Geisler
2010-06-23 18:02 ` Jakub Narebski
2010-06-23 19:19 ` Martin Geisler
2010-06-23 21:24 ` Jakub Narebski
2010-06-23 22:04 ` Martin Geisler
2010-06-23 19:36 ` Jay Soffian
2010-06-23 20:26 ` Junio C Hamano
2010-06-23 20:45 ` Jay Soffian
2010-06-24 20:31 ` Junio C Hamano
2010-06-24 22:49 ` Jay Soffian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=h2gadf1fd3d1004091633qe27d49f0m2ecb461e56f405b1@mail.gmail.com \
--to=santi@agolina.net \
--cc=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).