Talk:Misleading of parliament

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Possibly useful link[edit]

  • " Mr Speaker, as you well know, having been in this place longer than the member for Wyong, this is the most serious motion that can be moved against a Minister."
  • "the Westminster tradition, [...] is that if a Minister misleads the House once, he or she is meant to go. "

NSW Hansard

--Surturz (talk) 09:38, 27 June 2009 (UTC)[reply]

Other names[edit]

Here in the UK this is also known as "Misleading the House" (see Google) and it's also used in India, Canada, New Zealand and possibly more. Timrollpickering (talk) 05:50, 1 July 2009 (UTC)[reply]

External links modified (February 2018)[edit]

Hello fellow Wikipedians,

I have just modified one external link on Misleading of parliament. 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: 18 January 2022).

  • 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) 04:22, 2 February 2018 (UTC)[reply]