-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rip out merge-order and make "git log <paths>..." work again.
Well, assuming breaking --merge-order is fine, here's a patch (on top of the other ones) that makes git log <filename> actually work, as far as I can tell. I didn't add the logic for --before/--after flags, but that should be pretty trivial, and is independent of this anyway. Signed-off-by: Junio C Hamano <[email protected]>
- Loading branch information
Linus Torvalds
authored and
Junio C Hamano
committed
Mar 1, 2006
1 parent
70b006b
commit 765ac8e
Showing
11 changed files
with
82 additions
and
1,299 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,7 +16,7 @@ SYNOPSIS | |
[ \--no-merges ] | ||
[ \--remove-empty ] | ||
[ \--all ] | ||
[ [ \--merge-order [ \--show-breaks ] ] | [ \--topo-order ] ] | ||
[ \--topo-order ] | ||
[ \--parents ] | ||
[ \--objects [ \--unpacked ] ] | ||
[ \--pretty | \--header ] | ||
|
@@ -94,57 +94,10 @@ OPTIONS | |
topological order (i.e. descendant commits are shown | ||
before their parents). | ||
|
||
--merge-order:: | ||
When specified the commit history is decomposed into a unique | ||
sequence of minimal, non-linear epochs and maximal, linear epochs. | ||
Non-linear epochs are then linearised by sorting them into merge | ||
order, which is described below. | ||
+ | ||
Maximal, linear epochs correspond to periods of sequential development. | ||
Minimal, non-linear epochs correspond to periods of divergent development | ||
followed by a converging merge. The theory of epochs is described in more | ||
detail at | ||
link:http://blackcubes.dyndns.org/epoch/[http://blackcubes.dyndns.org/epoch/]. | ||
+ | ||
The merge order for a non-linear epoch is defined as a linearisation for which | ||
the following invariants are true: | ||
+ | ||
1. if a commit P is reachable from commit N, commit P sorts after commit N | ||
in the linearised list. | ||
2. if Pi and Pj are any two parents of a merge M (with i < j), then any | ||
commit N, such that N is reachable from Pj but not reachable from Pi, | ||
sorts before all commits reachable from Pi. | ||
+ | ||
Invariant 1 states that later commits appear before earlier commits they are | ||
derived from. | ||
+ | ||
Invariant 2 states that commits unique to "later" parents in a merge, appear | ||
before all commits from "earlier" parents of a merge. | ||
|
||
--show-breaks:: | ||
Each item of the list is output with a 2-character prefix consisting | ||
of one of: (|), (^), (=) followed by a space. | ||
+ | ||
Commits marked with (=) represent the boundaries of minimal, non-linear epochs | ||
and correspond either to the start of a period of divergent development or to | ||
the end of such a period. | ||
+ | ||
Commits marked with (|) are direct parents of commits immediately preceding | ||
the marked commit in the list. | ||
+ | ||
Commits marked with (^) are not parents of the immediately preceding commit. | ||
These "breaks" represent necessary discontinuities implied by trying to | ||
represent an arbitrary DAG in a linear form. | ||
+ | ||
`--show-breaks` is only valid if `--merge-order` is also specified. | ||
|
||
|
||
Author | ||
------ | ||
Written by Linus Torvalds <[email protected]> | ||
|
||
Original *--merge-order* logic by Jon Seymour <[email protected]> | ||
|
||
Documentation | ||
-------------- | ||
Documentation by David Greaves, Junio C Hamano and the git-list <[email protected]>. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.