Re: Beware dated Gerrit changes

[Guilhem Moulin]

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 `git fetch` or `git remote update`) which appears to
significantly reduce the amount of data to upload when running `git push`.
https://listarchives.libreoffice.org/global/website/msg15794.html

-- 
Guilhem.

PS. Sorry for breaking the thread, I don't have the Message-Id at hand.


signature.asc
Description: PGP signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Beware dated Gerrit changes

[Stephan Bergmann]

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 date.


I have filed  
"Color-code age of a patch set's parent" as a Gerrit enhancement idea 
now that might help spot such issues.


As a corollary, when creating a Gerrit change, make sure the change's 
parent is sufficiently recent to begin with.  Pull early, pull often.


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice