Follow-up Comment #8, bug #18210 (project freeciv):

Committed. Even to S2_2, which may have been unwise. It now occurred to me
that new behavior could be considered bug as much as old one, just by a bit
different logic. Let's hope that no caller depends on set_socket_errno() to
never change errno to value 0 in error situation.

I leave ticket open while I consider reverting that part of the patch from
S2_2 before 2.2.6 release just in case.


Reply to this item at:


  Message sent via/by Gna!

Freeciv-dev mailing list

Reply via email to