Page MenuHomePhabricator

Drive blame generation through `diffusion.blame`
ClosedPublic

Authored by epriestley on Jan 6 2016, 2:20 PM.
Tags
None
Referenced Files
F15474352: D14958.id36137.diff
Sun, Apr 6, 7:37 AM
F15455584: D14958.id36137.diff
Sun, Mar 30, 3:22 AM
F15449417: D14958.id36140.diff
Fri, Mar 28, 10:05 AM
F15445136: D14958.id.diff
Thu, Mar 27, 12:32 PM
F15439520: D14958.diff
Wed, Mar 26, 7:54 AM
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
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.