Re: potential improvement to 'git log' with a range

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]