Paths

Table of Contentst

Use consistent behavior between pubm:log and pub:log/dcc:log
ClosedPublic
Actions

Authored by dereckson on Mar 3 2018, 01:25.

Tags

None

Referenced Files

	F9609130: D1389.id.diff
	Mon, Jun 9, 23:24

	Unknown Object (File)
	Sun, Jun 8, 19:13

	Unknown Object (File)
	Tue, May 20, 04:39

	Unknown Object (File)
	Mon, May 12, 15:06

	Unknown Object (File)
	May 9 2025, 23:58

	Unknown Object (File)
	May 9 2025, 23:21

	Unknown Object (File)
	May 9 2025, 13:08

	Unknown Object (File)
	May 8 2025, 23:57

View All Files

Subscribers

None

Details

Reviewers

dereckson

Commits

rVIPER4349adfcb2f4: Use consistent behavior between pubm:log and pub:log/dcc:log

Summary

Sure, pubm:log has already identified the component and the entry,
but this is not a valid reason to violate SRP and make this hard
to maintain.

An hint it's a bad idea? former code used $emitter, which isn't defined.

Test Plan

Tested all day on #nasqueron-ops

Diff Detail

Repository

rVIPER ViperServ scripts

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

dereckson requested review of this revision.Mar 3 2018, 01:25

dereckson created this revision.

Harbormaster completed remote builds in B2179: Diff 3545.Mar 3 2018, 01:25

dereckson accepted this revision.Mar 3 2018, 01:25

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

This revision is now accepted and ready to land.Mar 3 2018, 01:25

Closed by commit rVIPER4349adfcb2f4: Use consistent behavior between pubm:log and pub:log/dcc:log (authored by dereckson). · Explain WhyMar 3 2018, 01:25

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

Wearg/

ServersLog.tcl

3 lines

Diff 3546

View Options

Use consistent behavior between pubm:log and pub:log/dcc:logClosedPublicActions