Talk:Course of the Rogue River (Oregon)

Latest comment: 7 years ago by InternetArchiveBot in topic External links modified

Main article edit

I split this course description off from the Rogue River (Oregon) article because the river article was at 85 kilobytes or so, not nearly complete, and because this particular course description overwhelms the other page. I'm not convinced that the description is complete, but it's getting close. It contains useful information, but it does not make a good just-for-fun read. I imagine it's rather like reading the phone book. I could not find another similarly large course description to imitate, and it might be that this is the longest. I cloned the templates from the Rogue River (Oregon) article's talk page and used them here. "Start-class" is probably not accurate on either page, but perhaps someone other than the main contributor should decide. Finetooth (talk) 03:20, 19 May 2009 (UTC)Reply

I changed it to C-class. Not sure I agree about high importance, though. tedder (talk) 22:18, 19 May 2009 (UTC)Reply
Thanks. I changed the importance level to "Mid" just now, although it might be "Low". I'm not sure. Finetooth (talk) 23:32, 19 May 2009 (UTC)Reply

External links modified edit

Hello fellow Wikipedians,

I have just modified one external link on Course of the Rogue River (Oregon). 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, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

 Y An editor has reviewed this edit and fixed any errors that were found.

  • 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) 16:53, 1 December 2016 (UTC)Reply