Made lensfun lookups for one lens really unique.  Fixes bug #9662.
Add keywords, as recommended here:

 http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html,
 http://bugs.debian.org/693918, and
 https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords
Proper english. 'allows one to', not 'allows to'
Keywords value MUST end with a semicolon
Use Exif.OlympusEq.LensType and give it precedence over
Exif.OlympusEq.LensModel and Exif.Photo.LensModel since it is normally
the most precise data and the string used in (the current svn of)
lensfun.
huge images: fix issues in pixelpipe, tiling, opencl, blend, gaussian, bilateral

still pending: masks, all modules
huge images: fix issues in masks
Merge branch 'master' into hugeimage
Merge pull request #438 from levitte/manpages

Proper english. 'allows one to', not 'allows to'
Add another form of pkg-config name for lua search.
huge images: fix issues in most iop's

exceptions: amaze demosaic and cacorrect
huge images: imageio and the like
increase default value of maximum_number_tiles to 10000
Use triggers to keep tagxtag consistency.

This lesser maintenance as lot of code to deal with tagxtag has
been removed. It also ensure proper consistency in the database.

This makes the code cleaner and probably a bit more efficient.
Minor code optimization.
Merge branch 'tagxtag-triggers'

* tagxtag-triggers:
  Minor code optimization.
  Use triggers to keep tagxtag consistency.
Merge branch 'hugeimage'

A set of maintenance patches to enable darktable to process images of (more or less) arbitrary
size. We can take advantage of the already long-established tiling mechanism. The only thing that
needed fixing is the type of variable used as index into image buffers. Our code used a lot of
type int (int32_t), which is now replaced by size_t. (No guarantee that I catched all cases - please
report problems)

To process huge images (e.g. stitched panoramas coming from Hugin) you need to have a look at the
settings of config parameter "host memory limit" (core options). It needs to be high enough to let
darktable take full advantage of all your system memory but not so high that your system runs into
HDD-swapping. You will also need to increase config parameter "maximum_number_tiles" (darktablerc)
to something like 10000 (the new default value).

If you are running darktable on a 32-bit system, don't even try to import anything bigger than an ordinary
RAW.
fix xml bug in last commit
Merge branch 'olympus-ft-lens-recognition' of https://github.com/fingerle/darktable
denoiseprofile: fix size_t striding issue