> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: vrijdag 24 januari 2014 16:47
> To: [email protected]
> Subject: svn commit: r1561041 - in /apr/apr/branches/1.5.x: ./
> include/apr_errno.h
> 
> Author: jim
> Date: Fri Jan 24 15:46:47 2014
> New Revision: 1561041
> 
> URL: http://svn.apache.org/r1561041
> Log:
> Merge r1561040 from trunk:
> 
> Using UDS, we sometime try ops not supported on UDS. Make this
> a known (and therfore handable) issue
> 
> Reviewed/backported by: jim
> 
> Modified:
>     apr/apr/branches/1.5.x/   (props changed)
>     apr/apr/branches/1.5.x/include/apr_errno.h
> 
> Propchange: apr/apr/branches/1.5.x/
> ------------------------------------------------------------------------------
>   Merged /apr/apr/trunk:r1561040
> 
> Modified: apr/apr/branches/1.5.x/include/apr_errno.h
> URL:
> http://svn.apache.org/viewvc/apr/apr/branches/1.5.x/include/apr_errno.h?
> rev=1561041&r1=1561040&r2=1561041&view=diff
> ==========================================================
> ====================
> --- apr/apr/branches/1.5.x/include/apr_errno.h (original)
> +++ apr/apr/branches/1.5.x/include/apr_errno.h Fri Jan 24 15:46:47 2014
> @@ -833,6 +833,13 @@ APR_DECLARE(char *) apr_strerror(apr_sta
>  #define APR_EAFNOSUPPORT  (APR_OS_START_CANONERR + 27)
>  #endif
> 
> +/** @see APR_STATUS_IS_EOPNOTSUPP */
> +#ifdef EOPNOTSUPP
> +#define APR_EOPNOTSUPP EOPNOTSUPP
> +#else
> +#define APR_EOPNOTSUPP    (APR_OS_START_CANONERR + 28)
> +#endif
> +
>  /** @} */
> 
>  #if defined(OS2) && !defined(DOXYGEN)
> @@ -977,6 +984,8 @@ APR_DECLARE(char *) apr_strerror(apr_sta
>                  || (s) == APR_OS_START_SYSERR + ERROR_ACCESS_DENIED)
>  #define APR_STATUS_IS_EAFNOSUPPORT(s)   ((s) == APR_AFNOSUPPORT \
>                  || (s) == APR_OS_START_SYSERR + SOCEAFNOSUPPORT)
> +#define APR_STATUS_IS_EOPNOTSUPP(s)     ((s) == APR_EOPNOTSUPP \
> +                || (s) == APR_OS_START_SYSERR + SOCEOPNOTSUPP)

Is this change allowed in apr 1.5.x or would this require bumping to 1.6.x on 
release?

In the Subversion project this wouldn't be allowed as public api change, and we 
would certainly document in which version this new value (and new check macro) 
was added.

        Bert

Reply via email to