Bump libclang API version after r262318

[kfunk]

Note: I don't have commit rights yet

[milianw]

lgtm - I should have done that directly. Sadly, I didn't receive my commit rights either yet ;-)

Manuel, sending a mail to Chris as outlined at http://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access is still valid?

[kfunk]

Bump? Waiting for another +1 here.

[kfunk]

@klimek: Ping?

[klimek]

+Benjamin as I have no clue when to update that number

[bkramer]

Bumping it is okay, it allows conditional compilation based on the number.

[kfunk]

Committed. Will use "Differential Revision: <id>" next time, forgot to amend...

commit d7ffc218c4adde4846b58b3aa4b56312f9442d61
Author: Kevin Funk <[e-mail]>
Date: Tue Mar 8 10:34:23 2016 +0000

Bump libclang API version after r262318

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@262922 91177308-0d34-0410-b5e6-96231b3b80d8

include/clang-c/Index.h

  * \brief The version constants for the libclang API.
  * CINDEX_VERSION_MINOR should increase when there are API additions.
  * CINDEX_VERSION_MAJOR is intended for "major" source/ABI breaking changes.
  *
  * The policy about the libclang API was always to keep it source and ABI
  * compatible, thus CINDEX_VERSION_MAJOR is expected to remain stable.
  */
 #define CINDEX_VERSION_MAJOR 0
-#define CINDEX_VERSION_MINOR 33
+#define CINDEX_VERSION_MINOR 34
 
 #define CINDEX_VERSION_ENCODE(major, minor) ( \
       ((major) * 10000)                       \
     + ((minor) *     1))
 
 #define CINDEX_VERSION CINDEX_VERSION_ENCODE( \
     CINDEX_VERSION_MAJOR,                     \
     CINDEX_VERSION_MINOR )