Re: RFR: 8347428: Avoid using secret-key in specifications [v2]

2025-02-03 Thread Sean Mullan
On Mon, 3 Feb 2025 19:18:23 GMT, Ben Perez wrote: >> There are quite some places in API specifications that use the term >> "secret-key". This is not a formal term. Consider replacing them with >> "secret key". > > Ben Perez has updated the pull request incrementally with one additional > comm

Re: RFR: 8347428: Avoid using secret-key in specifications [v2]

2025-02-03 Thread Ben Perez
> There are quite some places in API specifications that use the term > "secret-key". This is not a formal term. Consider replacing them with "secret > key". Ben Perez has updated the pull request incrementally with one additional commit since the last revision: fixed copyright dates --

Re: RFR: 8347428: Avoid using secret-key in specifications

2025-02-03 Thread Sean Mullan
On Tue, 28 Jan 2025 20:08:31 GMT, Ben Perez wrote: > There are quite some places in API specifications that use the term > "secret-key". This is not a formal term. Consider replacing them with "secret > key". Some of the copyright dates need to be updated. Also, I noticed another instance in

RFR: 8347428: Avoid using secret-key in specifications

2025-01-28 Thread Ben Perez
There are quite some places in API specifications that use the term "secret-key". This is not a formal term. Consider replacing them with "secret key". - Commit messages: - removed all instances of in docs/comments Changes: https://git.openjdk.org/jdk/pull/23342/files Webrev: h