On Tue, Dec 20, 2016 at 6:22 PM, Stephan Bergmann <sbergman@redhat.com>
wrote:
On 12/20/2016 01:44 PM, Huzaifa Iftikhar wrote:
Thanks for the reply, I understand the situation.
Should I wait for Norbert Thiebaud to reply or should I submit my patch
once again ?
Besides waiting for Norbert to eventually fix the underlying problem, you
can additionally:
* Either rebase your Gerrit change (e.g., in the Gerrit web UI, press the
"Rebase" button),
what does rebase do ?
* or prepare a new revision of your change (seeing that it received a -2
comment, so probably needs updating), and push that to Gerrit.
Should I submit a new commit or just amend changes and push it to the
existing patch ?
Either of those should trigger a new Jenkins build, and with some luck
that build will pick a Windows bot that doesn't run into this problem
(though with some bad luck, it might pick the "infected" bot again and fail
again).
Yeah I hope it builds successfully the next time.
[In the future, it's always better to keep the mailing list on CC with
follow-ups like this. Then others can add their comments, and you're not
necessarily waiting for only me to write an answer.]
Okay thanks I just did that :)
Context
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.