9/18: Notre Dame at Michigan State

• hangonsloopy

  

  Just posting what I happened to read. I'm not agreeing or disagreeing with it.
• Tiger2003

  

  karen lotz;491161 wrote:Interesting how every other delay of game gets called properly.

  
  I really don't think so I have seen numerous times, where the play clock hits zero and the referees don't call it.
• karen lotz

  

  Of course you have.
• hangonsloopy

  

  I've seen it happen countless times in the NFL and college. It was just magnified because of the moment in this game.
• karen lotz

  

  You have seen a play clock run out without delay of game being called countless times? Were you wearing scarlet and gray glasses when you saw it?
  
  
  Maybe you can't count higher than 1? Which would make sense.
• hangonsloopy

  

  karen lotz;491231 wrote:You have seen a play clock run out without delay of game being called countless times? Were you wearing scarlet and gray glasses when you saw it?
  
  
  Maybe you can't count higher than 1? Which would make sense.

  I see its impossible to have an intelligent conversation with you. I should have known better from reading the rest of the thread. If you've never seen the clock hit zero and the team snap the ball a fraction of a second later then you must not watch a lot of football.
  
  Go Bucks!
• karen lotz

  

  Yeah I have seen that happen, and its followed by a flag being thrown.
• vball10set

  I saw the game, and yes-the game clock was at zero and could/should have been called. However, it wasn't, and even though this will be debated ad nauseum for the next week or so, there's one thing we can all agree on--it won't be reversed. Time to move on.
• hangonsloopy

  

  karen lotz;491257 wrote:Yeah I have seen that happen, and its followed by a flag being thrown.

  
  haha fair enough. Enjoy being bitter.
• killer_ewok

  

  vball10set;491260 wrote:I saw the game, and yes-the game clock was at zero and could/should have been called. However, it wasn't, and even though this will be debated ad nauseum for the next week or so, there's one thing we can all agree on--it won't be reversed. Time to move on.

  I agree. I'll probably never get over it.....but we've got to let go sometimes and the bottom line is that it won't be reversed. Screwed or not, it's an L. I've complained about it as much as anybody but that's not going to make a difference. I'm just hoping that ND can upset Stanford.
• Tiernan

  killer_ewok;491323 wrote:I agree. I'll probably never get over it.....but we've got to let go sometimes and the bottom line is that it won't be reversed. Screwed or not, it's an L. I've complained about it as much as anybody but that's not going to make a difference. I'm just hoping that ND can upset Stanford.

  
  I personally think it was the greatest "Homer" job in CFB history and both the clock crew and officials knew exactly what was going on and probably confered together earlier to pull it off should the game come down to the wire like it did. And for the next 50 years Domers will bitch about how they got "Clock-Blocked" at MSU back in 0'10. Great stuff to add to your countless ad nauseum stories of "Tradition". Luckily there will be no need for clock antics this week...Stanford in a blow-out.
• killer_ewok

  

  LOL at "Clock-blocked."
  
  That was actually pretty good.
• Tiernan

  ^^^
  how many times have you used it already today?
• Sonofanump

  karen lotz;490263 wrote:http://www.und.com/allaccess/?media=195931
  
  about the 9:40 mark
  
  The back judge is looking directly at the play, doesn't throw the flag, it comes from behind the play.

  
  Just replying becuase I told you I would once we saw the video. Rogers Redding states that this call was too technical and marginal. However the ND player hitting the MSU player at the other 45 yard line should have been a personal foul.
  
  Did not see anything about the receiver being out of bounds.