Page MenuHomePhabricator

Drive blame generation through `diffusion.blame`
ClosedPublic

Authored by epriestley on Jan 6 2016, 2:20 PM.
Tags
None
Referenced Files
F13123644: D14958.diff
Tue, Apr 30, 11:36 AM
F13118458: D14958.diff
Mon, Apr 29, 2:25 PM
Unknown Object (File)
Thu, Apr 25, 10:19 PM
Unknown Object (File)
Wed, Apr 24, 10:55 PM
Unknown Object (File)
Fri, Apr 19, 4:03 PM
Unknown Object (File)
Wed, Apr 17, 2:20 PM
Unknown Object (File)
Sat, Apr 6, 9:09 PM
Unknown Object (File)
Tue, Apr 2, 12:56 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.