![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Paul Mackerras <paulus@samba.org> | |
| Mon, 17 Apr 2006 00:27:59 +0000 (10:27 +1000) | ||
| committer | Paul Mackerras <paulus@samba.org> | |
| Mon, 17 Apr 2006 00:27:59 +0000 (10:27 +1000) | ||
| commit | e7da347520486ce33bb77d241b574787c0ec18e8 | |
| tree | f25fca83a19468e17e830b1bffc8d1d3445458da | tree | snapshot |
| parent | c5a4c4debec43ff98053cb6b69d35d63e45ee131 | commit | diff |
gitk: Fix bug caused by missing commitlisted elements
This bug was reported by Yann Dirson, and results in an 'Error:
expected boolean value but got ""' dialog when scrolling to the bottom
of the graph under some circumstances. The issue is that git-rev-list
isn't outputting all the boundary commits when it is asked for commits
affecting only certain files. We already cope with that by adding the
missing boundary commits in addextraid, but there we weren't adding a
0 to the end of the commitlisted list when we added the extra id to
the end of the displayorder list.
This fixes it by appending 0 to commitlisted in addextraid, thus keeping
commitlisted and displayorder in sync.
Signed-off-by: Paul Mackerras <paulus@samba.org>
This bug was reported by Yann Dirson, and results in an 'Error:
expected boolean value but got ""' dialog when scrolling to the bottom
of the graph under some circumstances. The issue is that git-rev-list
isn't outputting all the boundary commits when it is asked for commits
affecting only certain files. We already cope with that by adding the
missing boundary commits in addextraid, but there we weren't adding a
0 to the end of the commitlisted list when we added the extra id to
the end of the displayorder list.
This fixes it by appending 0 to commitlisted in addextraid, thus keeping
commitlisted and displayorder in sync.
Signed-off-by: Paul Mackerras <paulus@samba.org>
| gitk | diff | blob | history |