Blame does work on those files locally. FWIW, fugitive vim's Gblame command has the ability to jump back to the blame of parent revision of the current line which makes it much easier to navigate history than any web based blame tool that I've seen. Even if you only use vim for GBlame I'd say it's still worth using.
-Jeff On Wed, Sep 16, 2015 at 2:13 PM, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 9/16/15 2:01 PM, Ehsan Akhgari wrote: >> >> Out of curiosity, which files are you mentioning here? > > > Here are some lovely links that all produce "This blame took too long to > generate. Sorry about that." for me: > > https://github.com/mozilla/gecko-dev/blame/master/layout/base/nsCSSFrameConstructor.cpp > > https://github.com/mozilla/gecko-dev/blame/master/dom/base/nsDocument.cpp > > https://github.com/mozilla/gecko-dev/blame/master/dom/base/nsGlobalWindow.cpp > > I have not done an exhaustive search for such files in our tree, but just > those three represent a significant fraction of my blame lookups... > > > -Boris > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
