Page MenuHomePhabricator

Drive blame generation through `diffusion.blame`
ClosedPublic

Authored by epriestley on Jan 6 2016, 2:20 PM.
Tags
None
Referenced Files
F19888693: D14958.id36140.diff
Tue, Mar 24, 3:46 AM
F19844181: D14958.id36137.diff
Mar 12 2026, 5:12 AM
F19812410: D14958.diff
Mar 4 2026, 4:54 AM
F19691446: D14958.id36140.diff
Feb 10 2026, 2:35 AM
F19676501: D14958.id36137.diff
Feb 8 2026, 12:02 PM
F19287526: D14958.diff
Dec 23 2025, 6:54 AM
F19153009: D14958.id.diff
Dec 11 2025, 6:46 AM
F18798625: D14958.id36137.diff
Oct 17 2025, 7:19 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.