Update the tls-client README.md #229
Conversation
There was a problem hiding this comment.
@RonEld Can you please explain the additional changes provided with this PR? I know that the data needed for the public access have changed, so I was expecting the changes to address that, however, it is not clear from the commit, why they were introduced.
I built and ran the example and I confirm that it still works, so I approve the PR in principle. However, I think it would be better for the sake of tracking the changes to split this PR into two commits with descriptive messages.
Update the tls-client application `README.md` as it mentions EasyConnect, and it is not true anymore.
Update links to a current location.
|
@k-stachowiak Thank yo for your review! I have split the commit to two, per your suggestion. |
|
@RonEld Thank you for addressing that. I still approve the PR. |
|
@sbutcher-arm - please review this PR, as it is targeted for 19.02. |
|
Bump @sbutcher-arm @k-stachowiak , you should merge this in... |
|
Nothing to do with me @JanneKiiskila, nor @k-stachowiak. We don't work on this. In actual fact, I think ownership has passed hands two or three times since this PR was opened. |
Update the tls-client application
README.mdasit mentions EasyConnect, and it is not true anymore. Update the links as
well.
Fixes #228