| commit | 3ae96885e53391fca4bed3ce23d57bfd05ea31b5 | |
| author | Jonas Fonseca <jonas.fonseca@gmail.com> | |
| Wed, 11 Mar 2015 03:08:13 +0000 (10 23:08 -0400) | ||
| committer | Jonas Fonseca <jonas.fonseca@gmail.com> | |
| Wed, 11 Mar 2015 03:21:35 +0000 (10 23:21 -0400) | ||
| tree | c69210717f4fb77c13594b185a4ee51b2e9db069 | treesnapshot (tar.gz zip) |
| parent | d2280ab6f5d71dd7a5f6b09dea696fc3d2821cd7 | commitdiff |
Use commit-order setting for controlling automatic topo-ordering
Remove the `commit-title-graph=no-topo` option and use `commit-order`
for setting whether or not to automatically use topo-ordering when the
graph is enabled. The main reason is that `commit-title-graph` is meant
for setting whether the graph is shown, whereas `commit-order` is the
perfect fit.
By default, `commit-order` is now set to "auto" which will do this.
However, users can set it to "default" (or any other commit order) to
disable this behavior. This matches the behavior of similar enum
settings that also have an "auto" value.
With this the main issues related with the performance degredation in
large repositories have been addressed and the two
Fixes #310
Fixes #324
Remove the `commit-title-graph=no-topo` option and use `commit-order`
for setting whether or not to automatically use topo-ordering when the
graph is enabled. The main reason is that `commit-title-graph` is meant
for setting whether the graph is shown, whereas `commit-order` is the
perfect fit.
By default, `commit-order` is now set to "auto" which will do this.
However, users can set it to "default" (or any other commit order) to
disable this behavior. This matches the behavior of similar enum
settings that also have an "auto" value.
With this the main issues related with the performance degredation in
large repositories have been addressed and the two
Fixes #310
Fixes #324