On Fri, 07 Aug 2020 at 14:39:29 +, Stephan Bergmann:
> As a corollary, when creating a Gerrit change, make sure the change's
> parent is sufficiently recent to begin with. Pull early, pull often.
A nice side-effect of doing that is that it'll update refs/remotes/logerrit/…
references (like `
In the fast-paced world of LibreOffice development, the Jenkins
Verified+1 of a Gerrit change's latest patch set may easily have become
irrelevant by the time the change is submitted, if there has been
sufficient change on the relevant git branch between the patch set's
parent and the submit da
