Re: [PATCH] gitweb.js: Harden setting blamed commit info in incremental blame
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 25, 2009, 21:39 UTC
- Message-ID
- <7vd436s2r8.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <200911252155.59318.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
> It was 'Unspecified error.' shown in xhr watch. Accessing xhr.status > causes an error.
As to the topic, it does not seem to break _existing_ features; if that is not the case, please let me know.
Otherwise I'm inclined to merge the entire series to 'master' by 1.6.6-rc1.
6821dee gitweb.js: fix padLeftStr() and its usage
6aa2de5 gitweb.js: Harden setting blamed commit info in incremental blame
e42a05f gitweb.js: fix null object exception in initials calculation
63267de gitweb: Minify gitweb.js if JSMIN is defined
c4ccf61 gitweb: Create links leading to 'blame_incremental' using JavaScript
e206d62 gitweb: Colorize 'blame_incremental' view during processing
4af819d gitweb: Incremental blame (using JavaScript)
aa7dd05 gitweb: Add optional "time to generate page" info in footer
-aef3768 gitweb: Use light/dark for class names also in 'blame' viewand treat it as a new feature with known breakages, to give it wider audience. That way you will hopefully get more people who are willing to help debug/fix things for you.