From: Junio C Hamano <gitster@pobox.com>
To: "Rafael Ascensão" <rafa.almas@gmail.com>
Cc: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git log print commits between a revision range (inclusive)
Date: Wed, 06 Mar 2019 08:52:17 +0900 [thread overview]
Message-ID: <xmqqimwwswum.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CACUQV5_VCYdBoi=Vz97KVSWipzf+tbi2wrkY1U2h4i78FxVY-w@mail.gmail.com> ("Rafael Ascensão"'s message of "Tue, 5 Mar 2019 23:42:22 +0000")
Rafael Ascensão <rafa.almas@gmail.com> writes:
> As Junio mentioned, "A..B" means all commits reachable from B except those
> reachable from A. Understanding this is just a way to say "B --not A" is
> important to know you can take advantage of:
>
> `--boundary`
> Output excluded boundary commits. Boundary commits are prefixed with -.
>
> In other words, git log --boundary <older hash>..<newer hash> should give you
> exactly what you asked with the small caveat it marks excluded commits
> differently.
You are correct, but only when dealing with a single strand of
pearls. If the history leading to <newer> is bushy with merges, the
above will give _far_ more than what was requested. The fork points
of the side branches that got merged during <old>..<new> will also
be shown, in addition to the <old>.
prev parent reply other threads:[~2019-03-05 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 7:28 Git log print commits between a revision range (inclusive) wuzhouhui
2019-03-04 7:30 ` wuzhouhui
2019-03-04 7:54 ` Junio C Hamano
2019-03-05 23:42 ` Rafael Ascensão
2019-03-05 23:52 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimwwswum.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rafa.almas@gmail.com \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).