Change-Id: I21360e2d65b64bc27f02d677eda05f9d9d765367

Change-Id: I6e63a545332a1b865a26b355db49869c214f97c7

Change-Id: I164afe17c3bff2f7d7f2b9daec0d5a5ca8fdf97a

Change-Id: Ic54337f4279daf78b099aab368eade5a6143f586

Change-Id: I69868ad65b6eb6405d5723cb4d65d5e30c72e3ae

Change-Id: Ia8a644c613de17279abdab533a6314ba6c0e0aec

Change-Id: Ie3c9bddcb4760d2fe2195c1ca0de7520e57d705f

Change-Id: Ie91376bf9c52238febdc15720bb7f4cd62ee2e08

Change-Id: Ia5607c977958317f3aca9061553cbfedb35944fa

Change-Id: Ifcd7410f659a76ac34f18bb561b2eaffa6ecbd3d
Reviewed-on: https://gerrit.libreoffice.org/724Reviewed-by: Andras Timar <atimar@suse.com>
Tested-by: Andras Timar <atimar@suse.com>

Change-Id: Ia84271c5fe7064bfa2d71b84da9fa4d9df945d51

Change-Id: I10433c3c40a0c648bd651ed786ecd5523bf58f61

Change-Id: Icfcdbedaf6b123fc726e2298ac47698940b36091

Change-Id: I39681fbf57c828e5d6e80ae7c3155f2f60410a1a

Change-Id: Idef3ee3fa246b314c4b6b8a59b2b366dadfb679a

Change-Id: I534aab7da0b05dadc3415856e57362ead57380c0

Change-Id: I8f1f5756ac777cefed52ae72af65931bfa14d580

Change-Id: Iec26cfb2f6715b12bed290d72e3a013d6a980544

Else, operator>>= flat out refuses to extract it, even though the particular value in this particular call would fit.
Also OSL_VERIFY the result of >>= (instead of ignoring it) to facilitate future detection of similar problem

Change-Id: I859c38c3589dc9e9ef5bdd882663aa3386a43237

Change-Id: I09a14fd50cf69cec8693b7058d105ee5f2998e02

Change-Id: I3ac81132e21710a2c1d974944a5bcd612d796ec6

Follow-up of 7fff9872. Buffer only cell formula values via
setCellFormulaValue. Otherwise we get crash in
FormulaBuffer::applyCellFormulaValues() as array/shared/datatable
formulas are treated differently

Change-Id: Ie344b273ec662e8af1bf9fa54e79614393634974

This reverts commit 34061bf6.
gb_PYTHON was moved again in dec68c66.

Change-Id: I8f73a804e2005108f4a47d9fe4f9cd4425787cb1

Change-Id: Ica30efee4fcd030dcc063321ba678a00bec726cd

Change-Id: I1a5f2fda44da782b43076eee67e292affe1bad1a

Change-Id: Iac8321655a18826f9adcf8aed8075cce1aa24652

...now that fa140733 "fix dep on internal ucpp"
moved things around, so use "=" instead of ":=" here.  (And I'm not sure the
other places need ":=" either.)

Change-Id: Id71570c4a55ab08ca339801dec78ef06cfd80ef0

...and some further clean up.

Change-Id: Id294c0f38fe0041646fc86cacbd2e19734c746a9

Change-Id: Ia17a714b55da06bd38c7b5d60881f1b3838da992

Change-Id: I44479648dd75142864503650494fb2e3f95fe719

Change-Id: If71b9a162b7deca5cc032bda206a8f580292ab91

The following tools are considered to be obsolete and are discontinued:
ldump, giparser, testhxx and support.

Change-Id: I70813c046edb30546463cda9eb8a1b96c3e840a3

which was removed in fde638b3

Change-Id: I57caf615f0ca49d0b90cb4c68b8ce8edf8f72a97
Reviewed-on: https://gerrit.libreoffice.org/723Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>

Change-Id: I444874a8b59ac82c807087fb1a1d958ab1f75b12

Change-Id: I42bbb3e53aaaad0e6b7df44ec2def038ac1a31eb

also add the support for the convention that a patch filename
encode the -p value if it end with .[0-9]
for instance foo.patch.2 indicate a -p2 patch

usage:

generate a 'reference' copy of the expanded and patched file structure
$> make clucene.clean
$> patches=t make clucene

go to the module
$> cd clucene

edit files in $WORKDIR/UnpackedTarball/clucene

force a rebuild of things that depend on that UnpackedTarball
$> make clucene.rebuild


create a -p1 patch named clucene.new.patch.1 in the module's directory
$> make clucene.genpatch

you can then rename it, place it where appropriate in the module
hierarchy, update the UnpackedTarball_lucene.mk to apply it.

rinse and repeat from the top (yes the make lucene.clean is needed
to regenerate a 'reference' expanded and patched tarball)

Change-Id: I419c54a5981cffa385521596ba5016d2ca7ef52a
Reviewed-on: https://gerrit.libreoffice.org/712Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>