I think it can still happen though. Imagine you're in a branch for large project P. You want to merge to trunk but there are conflicts. The upstream library

I think it can still happen though. Imagine you're in a branch for large project P. You want to merge to trunk but there are conflicts. The upstream library project L was changed in your branch but not in merged down by the submitter. Even if P simply relies on a binary of L that is already in the artifact store, you still have to deal with merging this code down when normally you wouldn't. In fact, the much bigger issue is that you now must deal with the double edged sword of updating the entire org when a shared dependency must be updated. Perhaps you even completed that task in your project branch. Now you get to deal with merging into every project in the org that was touched.