Change-Id: Ic30cdeffabec1eb1a6c153ac450a3d28064ef534

Change-Id: I3be2e72e5d4fbe879318e0cef48bfe0852f8bbbc

Change-Id: I4ebb1027151c3bc34f81fb1e13de6c4c5cfed54d

Was there since 2008-04-03 (with a format changed 2012-04-06)

Change-Id: Ib7fb741f5c39f3547002246706575ef0694009dd

jpeg_compress_struct gets padded with the same effect as the
jpeg_decompress_struct, so needs some reordering as well to make Mac/PPC
happy (a27a3990)

jpeg_decompress_struct gets padded when compiling libjpeg, but the
jpeg filter in svtools assume non-padded size, resulting in a mismatch
that makes libjpeg refuse to do its work.

...from 8046a87e.  At least sometimes in
sw_complex test (with various bundled Java extensions enabled) under load, this
code reports "Signal 11 during cups initialization called, ignoring cups" and
in-process JVM aborts in panic.  Looks like a legitimate SIGSEGV (to be
translated into java.lang.NullPointerException) from JVM code is erroneously
caught by the temporary lcl_signal_action in cupsmgr.cxx instead.  As there is
no non-cooperative way to have different signal handlers for different threads
(at least under POSIX), and
<https://issues.apache.org/ooo/show_bug.cgi?id=86306> "office crashes at startup
on Solaris Intel" suggests this signal-catching business is only there to work
around a completely broken machine, I think it is best to simply remove it
again.

Change-Id: I55b95a71d622f83c975989a4ffb1d95ef5737075

Change-Id: I804e8f27197314d913d2dde138391996338458aa

Change-Id: Ia77ea939f6ce9301afeabe1d1679998ce34b397e

Revert "and another wae ( that I missed )"

This reverts commit a1faa06b.

Revert "fix wae"

This reverts commit 2f588576.

Revert "attempt to prevent illegal maTabData access(s)"

This reverts commit 8352eb5a.

Conflicts:

	sc/source/ui/view/viewdata.cxx

Revert "fix bad stl access fdo#45987"

This reverts commit 8b1d29bc.

Conflicts:

	sc/source/ui/view/viewdata.cxx

Change-Id: Idba6ec8ab448332ec349f23b10a2cce8b313ff19
33c437c8b9f005c43f03518863e151a6f0fc9589

Change-Id: If5440cae646a56fef4c054774705689e5512b8e4

60cb70b9 specifically

Change-Id: I160b24505d3e2425ce807f92f80d6737b725941b

Change-Id: I0aff738968e286df57ef7dd5b67780108cdc6c89

+ do not check for "-" in the bug title; it might be also wide character
  in some cases

+ show result when looking for bug titles

+ sort bugs when loolking for bug titles and printing bug numbers

Change-Id: I39496f7d0cf5f7a116e7d3c506b76b4a3de1dee1

Change-Id: I3d5ecb3cc52aeba780087f4ecb6b3bf86353276c

Change-Id: I0d5bb5f593c94b039c45bde638337932fa380b55

Change-Id: I871c67582f60eb56e9ebda22e1b492ff2e321f6e

Change-Id: I5e46bf534d1b70536810e9d9ac0a67210b271109

Change-Id: Icddd688dbf5da8154dd470539b03b6a2d02ca755

Change-Id: Id7bd039b505d30e71065c2cdf27eba1cb466be56

Change-Id: Ieaaf2466474463d19f91c74ea7f164962ba19936

Change-Id: Ia7c1da0eedc5d64ef3f2b17fb999bec3b242af88

g++ (GCC) 4.7.0 20120507 (Red Hat 4.7.0-5:
/com/sun/star/uno/Sequence.hxx:178:10: error: assuming signed overflow
does not occur when assuming that (X - c) > X is always false
[-Werror=strict-overflow]

Unfortunately this --enable-dbg-util only problem (caused by
_GLIBCXX_DEUBG) resurfaced, perhaps because of new std::string based
logging in sal; adapt all map files to export the unique symbol.

... the output of "svninfo" in a directory that doesn't contain a .svn
changed

Change-Id: I16b132663a7c8d9fd60eafafecfc7f9e82b69b29

Change-Id: Ieb77f3b2da130edce01de61f86b1eba722fdb103

Change-Id: Ie4e41d8d7c5c598595aeef49091ebc7fc3cf300f

Change-Id: I9b774486e47484ada0c4f84ad8a4c23ed338da0d

Change-Id: If02be864f958de96ae1c54fe575b1828410390b1

Change-Id: Id2a12ec3a3c394bb40aa233f29807932b1fa84d5

Change-Id: I63344d31273cb0014f9d1767f8f36f78c9ff1bb8

Change-Id: Ieccb0e425cb505bec3735539ebdf154529fde330

Change-Id: I348a59b3c1b060a084680328aa07089b3c7ccc66

Change-Id: Ib68cbc8cbbd2b2b0b6f6069a3c6834c33eff8756

Change-Id: I57076fd1bef6d2b51f8d3c8f0338b5a715c206d0

Change-Id: Iee60b1d41f04f4a583c7392335068ca75668f42c

<w:p><w:pict>...<w:txbxContent><w:p><w:p/> - in this case, the inner
paragraphs should not interfere with the outer one, but e.g.
detecting whether it was the last paragraph in section could get
broken.

Change-Id: I8634ee6a0d6274f5770423ff798adfa260a33326

Change-Id: Iebfe536f228e7831d81d59ea3c3692f8906f72ad

Change-Id: Ie38913a9b41faae7c6017d05e501c65f4e07659a

See www.boost.org/doc/libs/1_49_0/libs/ptr_container/doc/tutorial.html#cloneability

Change-Id: Ie5409c598f2364bc86f296dac4e9f193213d45c4