Talk:1925 NFL Championship controversy

Latest comment: 3 years ago by 108.16.230.212 in topic OMG!
edit

Apparently this link ([1]) is broken. --Ahabvader (talk) 01:02, 12 December 2008 (UTC)Reply

Citation has been modified to link to the copy on archive.org. Zzyzx11 (Talk) 04:56, 12 December 2008 (UTC)Reply

What records?

edit

So the Green Bay Packers finished 8-5-1, the Yellow Jackets finished 13-8, and the other records remains a secret?-- Matthead  Discuß   13:42, 11 January 2009 (UTC)Reply

OMG!

edit

Is there anyone still alive that watched this season in person? —Preceding unsigned comment added by 210.23.129.201 (talk) 23:54, 26 January 2009 (UTC)Reply

Why does that matter?--108.16.230.212 (talk) 07:21, 19 October 2021 (UTC)Reply
edit

Hello fellow Wikipedians,

I have just modified 3 external links on 1925 NFL Championship controversy. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 18:40, 14 June 2017 (UTC)Reply