Page MenuHomePhabricator

Drive blame generation through `diffusion.blame`
ClosedPublic

Authored by epriestley on Jan 6 2016, 2:20 PM.
Tags
None
Referenced Files
F19287526: D14958.diff
Tue, Dec 23, 6:54 AM
F19153009: D14958.id.diff
Dec 11 2025, 6:46 AM
F18798625: D14958.id36137.diff
Oct 17 2025, 7:19 AM
F18796702: D14958.id36140.diff
Oct 17 2025, 4:02 AM
F18765181: D14958.id36137.diff
Oct 7 2025, 10:01 AM
F18713023: D14958.id.diff
Sep 29 2025, 5:35 AM
F18683723: D14958.diff
Sep 26 2025, 8:14 AM
F18640858: D14958.id36137.diff
Sep 18 2025, 6:56 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.