Don't escape '?'s in protocol output.
ClosedPublic
Actions

Authored by brooks on Jan 5 2018, 11:46 PM.

Tags

None

Referenced Files

	F133474648: D13779.diff
	Sun, Oct 26, 1:43 AM

	F133406581: D13779.id37573.diff
	Sat, Oct 25, 2:02 PM

	Unknown Object (File)
	Sat, Oct 18, 6:49 AM

	Unknown Object (File)
	Sun, Oct 12, 10:12 PM

	Unknown Object (File)
	Sun, Oct 12, 10:12 PM

	Unknown Object (File)
	Sun, Oct 12, 10:12 PM

	Unknown Object (File)
	Sun, Oct 12, 10:42 AM

	Unknown Object (File)
	Sep 24 2025, 5:19 PM

View All 59 Files

Subscribers

imp

Details

Reviewers

ngie
wblock
brooks

Group Reviewers

manpages

Commits

rS328422: MFC r328297:
rS328421: MFC r328297:
rS328297: Don't escape '?'s in protocol output.

Summary

This isn't required by mandoc and it's broken in groff.

PR: 224632

Diff Detail

Lint

Lint Passed

Unit

No Test Coverage

Build Status

Buildable 14148
Build 14320: arc lint + arc unit

Event Timeline

brooks created this revision.Jan 5 2018, 11:46 PM

brooks added a reviewer: manpages.Jan 6 2018, 9:30 PM

works for me so accepting so I can commit

This revision is now accepted and ready to land.Jan 23 2018, 8:02 PM

Closed by commit rS328297: Don't escape '?'s in protocol output. (authored by brooks). · Explain WhyJan 23 2018, 8:08 PM

This revision was automatically updated to reflect the committed changes.

Herald added a subscriber: imp. · View Herald TranscriptJan 23 2018, 8:08 PM

Revision Contents
Changeset List

Path

Size

usr.bin/

procstat/

procstat.1

6 lines

Diff 37573

View Options

usr.bin/procstat/procstat.1

Don't escape '?'s in protocol output.ClosedPublicActions