[swift-corelibs-dev] NSString.isAbsolutePath inconsistency
anthony.parker at apple.com
Thu Jan 19 16:23:08 CST 2017
If this was in master sometime before this past Tuesday, it should be included in the swift-3.1 branch by default (that branch received merges from master).
Did you check out the latest version of the swift-3.1 branch to verify that this change was missing?
> On Jan 19, 2017, at 4:23 AM, Nethra Ravindran via swift-corelibs-dev <swift-corelibs-dev at swift.org> wrote:
> Hi Philippe,
> A naming inconsistency with NSString.isAbsolutePath (file - NSPathUtilities.swift) was fixed in your PR named “ Import CoreFoundation changes from Sierra “:
> https://github.com/apple/swift-corelibs-foundation/commit/a455cde38e06052385560d0a7c5aeb5a4991f844 <https://github.com/apple/swift-corelibs-foundation/commit/a455cde38e06052385560d0a7c5aeb5a4991f844>
> However it appears that this PR hasn’t been cherry picked for swift-3.1-branch. I wanted to check if you plan to cherry-pick this PR for 3.1. If not I can raise a PR only for the NSString.isAbsolutePath inconsistency on the 3.1 branch.
> Please let me know what you think.
> Thank you.
> -Nethra Ravindran
> swift-corelibs-dev mailing list
> swift-corelibs-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-corelibs-dev