-
David Brownell authored
This gets rid of some potentially scarey messages I've recently seen on disconnect, "bad hash" for a TD ... it's really a "no hash" case, and this prevents the message in some cases where that's not an issue. Likely this is what Gary Gorgen noticed, but even he had a different problem, this message shouldn't always appear. It also slims down one other message, preventing it from appearing in the routine "protocol stall" case (and cluttering logfiles).
135c5b70