On Wed, Nov 18, 2015 at 8:27 PM, Norbert Thiebaud <nthiebaud@gmail.com>
wrote:
On Wed, Nov 18, 2015 at 2:28 PM, Ashod Nakashian
<ashnakash@gmail.com>
wrote:
(Sorry if this has already been discussed/considered.)
Once a patch is pushed to Gerrit a Jenkins build automatically
starts.
And
once subsequent patches are pushed the cycle repeats.
Is there a reason to keep running the builds of (old) patches that
will
not
get cherry picked?
Is there a reason to keep pushing these patches then ?
Just stop building patch over patch and pushing them in bulk.. and
make your patch independent of each other as much as possible.
Sorry, I didn't explain well.
The patches are related. They are updates based on feedback, partial
failure or improvement.
They aren't bulk pushes (whatever that means). They are updates on a
single
changeset.
Why do people send multiple patches per push? That's the right question
to
ask.
And the answer is: to improve the previous patch.
Hence my question. If a patch has partially failed, or I got feedback
to
improve it, or (insert reason here), and I want to push an update, why
should the previous patch still build when it's not necessary?
Hope this makes sense.
iow: make a patch, push it to gerrit, come back to 'master' make
another patch, push it to gerrit etc.
and _not_
make a patch, push it to gerrit
git pull -r
make another patch (on top of the non merged patch you just pushed to
gerrit), push it to gerrit => both patch get rebuilt
etc..
Obviously I'm not doing that. Obviously.
To me it looks completely wasteful to spend hours building a few
patches
that were pushed one after the other when only the last one is
relevant.
Then do not push new version of 'irrelevant' patches
Not
only it is wasteful to valuable shared resources, but the user is
punished
again, do not do that then.
Norbert
------------------------------------------------------------------------
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.