Because of name collision, that change masks potential shebang error in devel/plan9port which depends on shells/rc (plan9-like shell) which provides bin/rc.
It's one obscure port, so I guess that change is ok, but it would be nice to at least add comment about this potential issue.

Looks good for me.

It's no longer true since r209460 (for ~6.5 years).
Right now I586_CPU is mostly about 0xf00f bug:

Shouldn't you also free newfs_arg and mount_arg ?

• Don't check for valid fstype, rely on mount(8) for this
• Update -T option description

• Split long sentences.

• Bump manpage's date
• Rephrase -t option description
• Clarify -T option usage

As I understand, it will be a little hard to use both libjpeg and jpeg-turbo simultaneously with this implementation?
Also jpeg-turbo's run and build cases needs to be fixed: in former binaries renamed to PREFIX/bin/*-turbo to avoid conflict and in latter static library is not installed.

It looks fine, though .if ${PORT_OPTIONS:MPNGTEST} is kinda ugly. But please do exp-run before committing this. The libpng major version changes is always PITA and brings many ports breakages.

I think that all 3 @dir keywords can be removed.

Closed by commit rD45915 (authored by @ak).

So, what is the consensus about:

• gzip to compressed(term, not compress(1)) change
• clarification of PORTREVISION reset. I'm agree with wblock's suggestion.
• Removal 'repo churn' phrase.

Sync with github.com/freebsd/freebsd-ports-graphics repo:

• Fix mix of tab and spaces, make indentation consistent
• Cleanup of extra-devd patch
  • Use true/false instead od 0/1 as return value from the bool function
  • Combine two similar checks
  • Rearrange logic to remove goto and gratuitous continue
  • Add todo comment about usb_id
  • Misc: s/LogMessageVerb/LogMessage/, wrap comment, lowercase two error messages

Improve the comment for keyboard's check.

76 Why removing uhid?

Good catch! This is my local change sneaked in. My keyboard has multimedia keys which attach to uhid and xorg busies the device file. On the other hand, I've never seen mouse with uhid device. Perhaps there is no harm to keep this change.

I think someone ment doc and not doceng :-)

Doh. Fixed, sorry for the inconvenience.

28 the example is a gzip'ed tarball.

Yes, but I think that equate 'standard compressed tarball' to the tar.gz is too narrow.
Sure, it's still most popular format in the ports tree, but tar.bz2 and tar.xz represent a significant percentage of distfiles too. I think they also can be called an 'standard compressed tarball'.

Is there a reason doceng@ is added, instead of a more wider audience?
I see no reason for doceng@ to be involved in review of such a trivial change.

I apologize, someone recommended me to add doceng@ as reviewer for handbook.