sync up security.xml after recent update to reporting.xml to not cause confusion for end-user
ClosedPublic
Actions

Authored by jgh on Mar 27 2015, 3:18 AM.

Tags

None

Referenced Files

	Unknown Object (File)
	Nov 6 2024, 9:11 PM

	Unknown Object (File)
	Oct 5 2024, 7:31 PM

	Unknown Object (File)
	Oct 5 2024, 8:49 AM

	Unknown Object (File)
	Oct 2 2024, 6:25 PM

	Unknown Object (File)
	Oct 2 2024, 12:58 AM

	Unknown Object (File)
	Oct 1 2024, 1:41 AM

	Unknown Object (File)
	Sep 30 2024, 6:15 PM

	Unknown Object (File)
	Sep 27 2024, 8:46 AM

View All 44 Files

Subscribers

None

Details

Reviewers

wblock
remko
bcr

Commits

rD46385: - follow r46381 and sync security page

Diff Detail

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

jgh updated this revision to Diff 4452.Mar 27 2015, 3:18 AM

jgh retitled this revision from to sync up security.xml after recent update to reporting.xml to not cause confusion for end-user.

jgh updated this object.

jgh edited the test plan for this revision. (Show Details)

jgh added reviewers: bcr, remko, wblock.

jgh set the repository for this revision to rD FreeBSD doc repository - subversion.

wblock added inline comments.Mar 27 2015, 3:26 PM

htdocs/security/security.xml
26	"operating system" should not be capitalized.

If this is the case, then I can update this and the reporting.xml, where operating system was approved.

Was approved in upper-case.

addressed comments

Sorry, I missed that. Yes, the words should be lower case, as opposed to the acronym "OS".

This revision is now accepted and ready to land.Mar 27 2015, 3:39 PM

jgh closed this revision.Mar 27 2015, 4:03 PM

Revision Contents
Changeset List

Path

Size

htdocs/

security/

security.xml

3 lines

Diff 4463

View Options

htdocs/security/security.xml

sync up security.xml after recent update to reporting.xml to not cause confusion for end-userClosedPublicActions