Hacker News Reader

Mac: What implication?

Dennis: The implication that things might go wrong for her if she doesn't review my code in a timely manner. Now, not that things are gonna go wrong for her, but she’s thinking that they will.

The others have one thing in common: they describe the difference between what is and what should be. Whereas diff is commonly used for the difference between any two things. You could make a diff (as in using the diff program) between two feature branches with no intention of merging one into the other. To me it makes sense to have separate names for these two concepts.

Diff seems the best because the others describe internal details of the source code management implementation. Pull request, merge request, and changelist especially.

They are all diffs. Simple is better here.

All pull/change/merge requests are diffs, but not all diffs are pull/change/merge requests.

Right, but in the context of making code changes, you can use diff. Which aligns with the Unix tool diff, and application of said diff with patch. So diff and patch are the operations that happen as you mutate a code base.