GSoC 2018 Help
pranavk at collabora.co.uk
Mon Mar 12 04:01:37 UTC 2018
(Please keep @libreoffice in CC)
On 11/03/18 19:04, Apurva Pavaskar wrote:
> Needed to ask some more things :
> -the subsequent builds will automatically be incremental right?
Yes, unless you touch some widely used header files.
> -for filing a bug/working on one : do I need to do it through bugzilla or
> gerrit? and how?
If you have found a bug, it's best to file it on bugzilla first and then submit
fixes/patches for it in gerrit (mentioning the bug number in the commit message).
Regarding how, you might want to look at these:
> -how do I pull the latest changes before building my build and submitting my patch?
`git pull` should be enough to pull the latest changes and rebase your current
changes on top of that.
> And there is an easy hack on Bugzilla : Bug 55410
> I wanted to fix it for KDE rather than windows, how do I file in a new bug
> (gerrit/bugzilla) and how?
Comment 16 reports that it's broken for Linux as well. Also, the bug fields
doesn't mention it to be a Window specific bug; so, no need to file a separate bug.
You might want to read the commit that breaks it for Linux. Did you already do
that? If yes, I think it's best to dump your findings on the bug so that others
can help you wherever you are stuck.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the LibreOffice