Page MenuHomePhabricator

Drive blame generation through `diffusion.blame`
ClosedPublic

Authored by epriestley on Jan 6 2016, 2:20 PM.
Tags
None
Referenced Files
F15423203: D14958.id36140.diff
Sat, Mar 22, 1:54 PM
F15412602: D14958.diff
Wed, Mar 19, 1:57 PM
F15400630: D14958.id.diff
Mon, Mar 17, 1:01 PM
F15343185: D14958.id36140.diff
Sun, Mar 9, 10:14 PM
F15343184: D14958.id36137.diff
Sun, Mar 9, 10:14 PM
F15343182: D14958.id.diff
Sun, Mar 9, 10:14 PM
F15335685: D14958.id36137.diff
Sat, Mar 8, 5:22 PM
F15335533: D14958.diff
Sat, Mar 8, 4:10 PM
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.