On Sat, Nov 8, 2014 at 9:50 AM, Maarten Hoes <hoes.maarten@gmail.com> wrote:
On Fri, Nov 7, 2014 at 8:55 PM, Norbert Thiebaud <nthiebaud@gmail.com>
wrote:
This is not really part of the product we package... os just put an
appropriate open-source license statement at the to of the script.
and prolly the best is to find a place for it in 'buildbot.git'
(accessble via gerrit)
So where does this 'buildbot.git' live, and how do I set up submit
access to
that so I can commit the script ?
as I said :-) gerrit.
gerrit.libreoffice.org/buildbot
Okay, so did 'git clone git://gerrit.libreoffice.org/buildbot', and
registered for an account over at gerrit and committed my public ssh key. S
same process to upload patches than core.git :-)
Which is ? Pointer to some docs or an explanation would be appreciated.
Thanks.
nevermind, I guess this is it:
https://wiki.documentfoundation.org/Development/gerrit
one more question: is it possible to change your gerrit username after you
have set it to something ? Id like to change it, but it seems the gerrit
html gui doesnt allow you to change it. Deleting and creating the account
again is fine I guess, but I cant find options to delete the account
anywhere either.
Thanks.
- Maarten
Context
- Re: 'master' 'make check' lcov code coverage report (continued)
Re: 'master' 'make check' lcov code coverage report · Maarten Hoes
Re: 'master' 'make check' lcov code coverage report · Norbert Thiebaud
Re: 'master' 'make check' lcov code coverage report · Maarten Hoes
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.