tig-2.0.3 has been release with this fix:
https://github.com/jonas/tig/commit/adb362bd657cc474629557310dfab12051bb61ac
On Tue, Aug 12, 2014 at 9:57 PM, Jonas Fonseca wrote:
> A temporary work-around is to add the following to your ~/.tigrc:
>
> set commit-order = topo
>
> to enable the work-a
A temporary work-around is to add the following to your ~/.tigrc:
set commit-order = topo
to enable the work-around for all repositories or alternatively add
the following line on a repository basis in the .git/config file
[tig] commit-order = topo
The problem is that the default commit
Hi Simon,
This is indeed a regression. The graph rendering was reworked extensively
in version 2.0 to fix several other bugs. I'll investigate if a fix can be
made for tig version 2.0.3 and keep you informed.
On Aug 10, 2014 11:09 AM, "Simon Paillard" wrote:
> Package: tig
> Version: 2.0.2-1
> S
Package: tig
Version: 2.0.2-1
Severity: normal
Dear Maintainer,
The way tig displays branches/merges on with a standard debian
git workflow was way better in 1.2.1-1 than in 2.0.2-1.
This makes the display rather difficult to read.
Indeed, tig 2.0.2-1 adds one more column for each merge perform
4 matches
Mail list logo
