I've noticed that specific commits sometimes disappear from the master
branch. Is this an inevitable consequence of the way Arrow does releases?
Or would it be possible to avoid removing commits from the master branch?

Of course once we start using Arrow releases this won't be an issue. At the
moment we check out specific Arrow commits, and so there are a number of
commits in our history that no longer build because the corresponding
commits in Arrow have disappeared.

Reply via email to