Are you sure it's the case for GitHub? I know it happens kinda often on BitBucket since they include git version in footer, but GitHub doesn't do that. I believe patch will never change unless repository history would be rewritten which would change commit hash (and then link to commit will change). But I'd say it would be even better to fail from our side then, to catch the fact of history rewrite.

@vsasjason_gmail.com I know it but there is reason I don't use. When the source of patch is GitHub, content of the file sometimes changes with unknown reason and it causes checksum error. So I intentionally include patch file in ports tree.

Change reviewer to new maintainer.

Replase files/patch-server-fn.c with the patch from upstream.

I confirmed make -j 8 buildworld buildkernel update-packages works as is expected by applying the diff.

After applying D52167 to latest ports tree, I tried to apply this one
but it failed as below.

• Chase update of databases/pg.el
• Update commit message