Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi Regina,

On Mon, Aug 31, 2015 at 11:00 PM, Regina Henschel
<rb.henschel@t-online.de> wrote:
Christian Lohmaier schrieb:

You need to rebase your patch to a working state. When there is a new
revision of the patch, jenkins will pick it up automatically..

Please keep in mind, I really Newbie here. How do I do that?

If it is a more or less self-contained change where it is unlikely
that other people's changes cause conflicts, you can  do so from
gerrit webinterface - when logged in there's a rebase button (next to
the Abandon one)

I have already
made "git pull -r" and build again. Next step?

To  rebase manually, just resubmit again. As long as the Change-ID in
the commit-message is the same, gerrit can keep track and will create
a new revision of the patch.

Note that you should do all your gerrit-commits in a separate branch,
so you can update multiple changes individually, without introducing
unnecessary dependencies.

ciao
Christian

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.