I: approaching 4.5.20 release

[Roland McGrath]

> I have no RHEL4/ppc nearby to check potential fixes, so even if I could
> guess a fix I wouldn't be able to check it.  Also, any change in this
> area may cause build regressions on other platforms.  This is not the kind
> of changes I'd apply right before release.

Agreed.

> That is, I think that commit v4.5.19-40-gacbe518 is ready to be tagged
> as v4.5.20.

Looks fine to me.  Will you do the honors on sourceforge?


Thanks,
Roland