From: Aghiles <aghilesk@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, git list <git@vger.kernel.org>
Subject: Re: potential improvement to 'git log' with a range
Date: Sun, 11 Apr 2010 16:31:51 -0400 [thread overview]
Message-ID: <k2r3abd05a91004111331ld522220ehfffeb65c45040a94@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004091807220.3558@i5.linux-foundation.org>
On Fri, Apr 9, 2010, Linus Torvalds wrote:
> Well, technically ".." means two different things
>
> - for "set operations" (ie "git log" and friends) it's the "relative
> complement" of two sets (or "'reachable from A' \ 'reachable from B'").
>
> - for "edge operations" (ie "git diff" and friends) it's just two
> end-points (aka "range"). A diff doesn't work on sets, it only works on
> the two endpoints.
OK.
> Most SCM's really talk about "ranges". Once you think in those terms,
> complex history doesn't work. Git very fundamentally is much about set
> theory, and "ranges" is a bad word to use.
I see how ranges are not powerful enough for complex history. It is just
that for me (and maybe for some others), the ".." sign has a strong
association with "range".
Thank you very much for the explanation,
-- aghiles
next prev parent reply other threads:[~2010-04-11 20:32 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
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 [this message]
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=k2r3abd05a91004111331ld522220ehfffeb65c45040a94@mail.gmail.com \
--to=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
--cc=torvalds@linux-foundation.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).