In D37540#853610, @emaste wrote:

I wonder how this ever worked.

Maybe in practice the first allocation setting argmax to 32 ends up being sufficient?

I do wonder if /.cshrc should survive the pkgbase transition.

I like the idea of moving in this direction.

Seems reasonable. I'd probably put the addition on a separate line.

In D37312#847847, @diizzy wrote:

@brooks Submit it upstream if applicable?

I've tested this as far as running the built ksh trivially and aarch64. Unfortunately make test blew up with a mktemp usage error that I've not dug into yet.

Seems generally reasonable. Do we need to check afterwards to warn if they were not deleted?

I think I lean toward "add them when their absence is annoying" as an initial policy. It might be worth some experiments to see if the result of adding all whitespace-only commits is measurable though.

Committed in rG0eea46fb1f83f. It's unclear to me why this didn't close...

In D36620#835783, @koobs wrote:

Could you list deprecation/removal here please: https://wiki.freebsd.org/DeprecationPlan

This change is what was supposed to happen with the generated smoke test. Too bad it's the first case I can think of in about 5 years...

The "you can't even do math" thing always seems excessive, but if gcc is going to warn on it then at least it will clean up all the CHERI realloc issues.

Not sure I've followed all the signal details, but I understand the basic design and it makes sense to me.

Restore a couple more important references adding a reference to the
port. This follows existing inetd.8 practice.

• Drop UPDATING entry