gitweb: correctly store previous rev in javascript-actions mode

Git fork

Without this change, the setting

$feature{'javascript-actions'}{'default'} = [1];

in gitweb.conf breaks gitweb's blame page: clicking on line numbers
displayed in the second column on the page has no effect.

For comparison, with javascript-actions disabled, clicking on line
numbers loads the previous version of the line.

Addresses https://bugs.debian.org/741883.

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Robert Luberda <robert@debian.org>
Acked-by: Jakub Narębski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

authored by

Robert Luberda and committed by

Junio C Hamano 6 years ago 52bd3e46 5fa0f523

+1 -1

1 changed file

expand all

unified split

gitweb

static

blame_incremental.js

+1 -1

gitweb/static/js/blame_incremental.js

··· 484 484 case 'previous': 485 485 curCommit.nprevious++; 486 486 // store only first 'previous' header 487 - if (!'previous' in curCommit) { 487 + if (!('previous' in curCommit)) { 488 488 var parts = data.split(' ', 2); 489 489 curCommit.previous = parts[0]; 490 490 curCommit.file_parent = unquote(parts[1]);