From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: RE: [PATCH] revisions(7): clarify that most commands take a single revision range
Date: Fri, 21 May 2021 14:19:20 -0500 [thread overview]
Message-ID: <60a807b82f6aa_558062081c@natae.notmuch> (raw)
In-Reply-To: <xmqqv97g2svd.fsf@gitster.g>
Junio C Hamano wrote:
> +Commands that are specifically designed to take two distinct ranges
> +(e.g. "git range-diff R1 R2" to compare two ranges) do exist, but
> +they are exceptions. Unless otherwise noted, all "git" commands
Not sure why "git" is in quotes.
> +that operate on a set of commits work on a single revision range.
> +In other words, writing two "two-dot range notation" next to each
> +other, e.g.
> +
> + $ git log A..B C..D
> +
> +does *not* specify two revision ranges for most commands. Instead
> +it will name a single connected set of commits, i.e. those that are
> +reachable from either B or D but are reachable from neither A or C.
> +In a linear history like this:
> +
> + ---A---B---o---o---C---D
> +
> +because A and B are reachable from C, the revision range specified
> +by these two dotted ranges is a single commit D.
For example, if you have a linear history like this:
---A---B---C---D---E---F
Doing A..F will retrieve 5 commits, and doing B..E will retrieve 3
commits, but doing A..F B..E will not retrieve 8 commits. Instead the
starting point A gets overriden by B, and the ending point of E by F,
effectively becoming B..F.
With more complex graphs the result is not so simple and might result
in two disconnected sets of commits, but that is considered a single
revision range.
--
Felipe Contreras
prev parent reply other threads:[~2021-05-21 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 11:17 [PATCH] revisions(7): clarify that most commands take a single revision range Junio C Hamano
2021-05-20 2:27 ` Bagas Sanjaya
2021-05-20 4:58 ` Junio C Hamano
2021-05-20 5:02 ` Junio C Hamano
2021-05-20 5:26 ` Bagas Sanjaya
2021-05-20 16:45 ` Elijah Newren
2021-05-20 16:53 ` Eric Sunshine
2021-05-20 16:40 ` Elijah Newren
2021-05-21 19:19 ` Felipe Contreras [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60a807b82f6aa_558062081c@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).