Adrien Destugues a558d18527 Revert "filesystems: we aren't BeOS, so we can safely use -O2(+)." ... This reverts commit ae495ca8fe. My system volume was mysteriously corrupted while booting or shutting down today, enough to make it unbootable and KDL on attempt to mount it. I'm assuming our gcc2 still isn't safe with regard to -O2 optimization of filesystems, and revert this, until proven wrong (eg. by running test suites and FS stress tests and finding no issues. Axel comented on the commit saying it probably was not a good idea, but no action was taken. Should we setup a better commit review system?		2015-06-22 18:51:03 +02:00
..
add-ons	Revert "filesystems: we aren't BeOS, so we can safely use -O2(+)."	2015-06-22 18:51:03 +02:00
apps	VideoProducer: fix the fix.	2015-06-15 21:00:14 +02:00
bin	…
build	…
data	Update pci.ids from pciids.sourceforge.net	2015-06-18 05:20:28 +02:00
kits	Fix mess in Tracker add-ons created in hrev48858	2015-06-20 19:39:54 -07:00
libs	freebsd_network: add __UNCONST	2015-06-14 15:46:50 +02:00
preferences	…
servers	package_daemon: queue post-install scripts to run after reboot	2015-06-15 13:36:13 +12:00
system	Replace a few references to Subversion with Git.	2015-06-19 15:36:52 -04:00
tests	Revert "filesystems: we aren't BeOS, so we can safely use -O2(+)."	2015-06-22 18:51:03 +02:00
tools	Revert "filesystems: we aren't BeOS, so we can safely use -O2(+)."	2015-06-22 18:51:03 +02:00
Jamfile	…