On 2017-01-23, at 2:38 AM, Konstantin Khomoutov <flatw...@users.sourceforge.net> wrote: > ... > > In particular, refer to: > > * the `git log` manual for the description of the > "-Sstring" command-line option (the mode it enables is called > "pickaxe"; see also "--pickaxe-regex" and "--pickage-all" modifiers to > it, and the "-G" command-line option); > * to the `git rev-list` manual for the "--branches" option; > * and the gitrevisions manual for the ^commit notation.
... and, to something called "gitdiffcore" ... gee, this is exactly where those "smart tools" that Linux was talking about are found. So this is the first I've heard of "diffcore". I'm not even using "diff-tree", "diff-index", or "diff-files" -- but I'm sure that everything else uses them. === Now, in reading all this, I'm realizing I have a fundamental misunderstanding of git. To me, the commits reachable from a given commit are those that come after it. The future from the commit. To git, it's the exact opposite. The history before the commit. This makes sense -- a commit object records all the heads that were merged together to make it, so a commit records its past, not its future. So how does git determine the future from commit X when the data only tracks the history before X? === Can someone give me a better understanding of ".." and "..."? I thought ".." meant "everything from A to B", but apparently it is actually more general than that, and I don't understand "..." at all. --- Entertaining minecraft videos http://YouTube.com/keybounce -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
