> That's why I'm half inclined to think that the current situation is better.
See also bug 2028288. The solution for that bug may require us to force push the branch pointers following deletions. If we do that then we'll be choosing the other side of the coin: higher version strings "already burned" wouldn't be well understood by developers.
> That's why I'm half inclined to think that the current situation is better.
See also bug 2028288. The solution for that bug may require us to force push the branch pointers following deletions. If we do that then we'll be choosing the other side of the coin: higher version strings "already burned" wouldn't be well understood by developers.