mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-02-03 18:20:29 +01:00
nm-version.h: use the right value of NM_API_VERSION
After the changes in release.sh in previous commits, during development the value of NM_VERSION will always be the next version, not the latest released one. As a consequence, we don't need to set MICRO+1 in NM_API_VERSION, which was a temporary workaround.
This commit is contained in:
parent
c0fe80ff87
commit
36275bc51c
1 changed files with 3 additions and 3 deletions
|
|
@ -83,15 +83,15 @@
|
|||
|
||||
/* For releases, NM_API_VERSION is equal to NM_VERSION.
|
||||
*
|
||||
* For development builds, NM_API_VERSION is the next
|
||||
* stable API after NM_VERSION. When you run a development
|
||||
* For development and RC builds, NM_API_VERSION is the next
|
||||
* stable API after NM_VERSION. When you run a devel or RC
|
||||
* version, you are already using the future API, even if
|
||||
* it is not yet released. Hence, the currently used API
|
||||
* version is the future one. */
|
||||
#define NM_API_VERSION \
|
||||
(((NM_MINOR_VERSION % 2) == 1) \
|
||||
? NM_ENCODE_VERSION(NM_MAJOR_VERSION, NM_MINOR_VERSION + 1, 0) \
|
||||
: NM_ENCODE_VERSION(NM_MAJOR_VERSION, NM_MINOR_VERSION, NM_MICRO_VERSION + 1))
|
||||
: NM_VERSION)
|
||||
|
||||
/* deprecated. */
|
||||
#define NM_VERSION_CUR_STABLE NM_API_VERSION
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue