Gervase Markham wrote:
Basically, the principle was, for a given release: - Find the release tag - Get client.mk on that tag - Find the value of NSS_CO_TAG in client.mk - Find the version of certdata.txt on that new tag - Record the version number, and what bugs were checked in after it left the trunk
Your last step is not clear, but I believe your method is correct. - certdata.txt is the file that contains the built-in root CA certificates. - the version of certdata.txt needs to determined using the method you described above. Wan-Teh _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
