Providence-UConn

[PGsHeroes32]

MU is going to get the absolute sh** beat out of them.

My low confidence in playing Uconn just slightly increased thanks to this.

[ATL MU Warrior]

For all the love that Cooley gets on here, that was an absolutely boneheaded decision to foul when a 10 second violation was going to occur in less than 2 seconds and the center with the ball looking like a deer in the headlights.

If a certain former MU coach had let that happen he'd be berated for days on end for his stupidity and deservedly so.

[nyg]

What time's the Wisconsin game tonight?

See, that's the issue. Just don't reply to their posts. I know it's hard, but if everyone manned up, read or don't read the posts, just don't reply.  That's what they want, a reaction. 

[Jockey]

See, that's the issue. Just don't reply to their posts. I know it's hard, but if everyone manned up, read or don't read the posts, just don't reply.  That's what they want, a reaction.

Yup. They think their post will make a difference. And it does. It encourages the trolls even more.

[wisblue]

For all the love that Cooley gets on here, that was an absolutely boneheaded decision to foul when a 10 second violation was going to occur in less than 2 seconds and the center with the ball looking like a deer in the headlights.

If a certain former MU coach had let that happen he'd be berated for days on end for his stupidity and deservedly so.

I was watching at the time and can't remember if there was something that caused the 10 second count to reset.

[cheebs09]

I was watching at the time and can't remember if there was something that caused the 10 second count to reset.

A timeout was called. I thought that reset it.

[StillAWarrior]

Yup. They think their post will make a difference. And it does. It encourages the trolls even more.

Agreed.

You know what really shuts them up? Creating new threads for them -- with their names in the thread title! That'll teach them...they hate attention.

Just. Ignore. Please.

[wisblue]

A timeout was called. I thought that reset it.

If there was a timeout that does reset the count.

[ATL MU Warrior]

A timeout was called. I thought that reset it.

No, they fouled Sonogo to stop the clock with the shot clock at 22. 

[JWags85]

No, they fouled Sonogo to stop the clock with the shot clock at 22.

UCONN called a timeout with 23 on the clock, which I think resets the 10 second count.  So thats why they fouled Sonogo on the inbound.

[ATL MU Warrior]

UCONN called a timeout with 23 on the clock, which I think resets the 10 second count.  So thats why they fouled Sonogo on the inbound.

The timeout was after the foul. Smart move by Hurley.

[mugrad_89]

UCONN called a timeout with 23 on the clock, which I think resets the 10 second count.  So thats why they fouled Sonogo on the inbound.

There was a kick ball with 3 seconds left and then Hurley called the timeout which reset the 10 second count.

[ATL MU Warrior]

There was a kick ball with 3 seconds left and then Hurley called the timeout which reset the 10 second count.

A providence player fouled Sanogo who was looking for someone to pass to. There was no kicked ball as there was no pass. After the foul Hurley wisely called a timeout so the shot clock would reset.

The foul occurred with either 22 or 23 seconds left on the shot clock so in my view, Providence should NOT have fouled as UConn's center had the ball and was not even thinking about advancing via the dribble. It was a sure :10 violation if Providence had just continued playing defense.

[wadesworld]

Looks like timeout by UCONN, then foul on Providence.

[ATL MU Warrior]

Looks like timeout by UCONN, then foul on Providence.

Darn it. I guess my memory sucks.