Page MenuHomePhabricator

Drive blame generation through `diffusion.blame`
ClosedPublic

Authored by epriestley on Jan 6 2016, 2:20 PM.
Tags
None
Referenced Files
F13297884: D14958.diff
Fri, Jun 7, 6:01 AM
F13260093: D14958.diff
Sun, May 26, 11:29 PM
F13258859: D14958.id36140.diff
Sun, May 26, 1:29 PM
F13242535: D14958.diff
Thu, May 23, 2:51 AM
F13236162: D14958.id36137.diff
Tue, May 21, 8:31 AM
F13236023: D14958.id.diff
Tue, May 21, 7:39 AM
F13235494: D14958.id36140.diff
Tue, May 21, 5:33 AM
F13234128: D14958.id.diff
Tue, May 21, 3:02 AM
Subscribers
None

Details

Summary

Ref T2450. Ref T9319. This is still a bit messy, but not quite so bad as it was: instead of using a single call to get both blame information and file content, use diffusion.blame for blame information.

This will make optimizations to both blame and file content easier.

Test Plan

Viewed a bunch of blame (color on/off, blame on/off).

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Drive blame generation through `diffusion.blame`.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Jan 6 2016, 3:13 PM
This revision was automatically updated to reflect the committed changes.