Saints release Brett Sharman after Mo Farah tweet

 

Wyn Griffiths
Friday 24 August 2012 17:23 EDT
Comments

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Brett Sharman, who posted an offensive tweet about the double Olympic gold medallist Mo Farah on Twitter, has been released by Northampton.

The 25-year-old had been under investigation by Saints after he posted the tweet, for which he later made an apology.

The club said Sharman had left Franklin's Gardens because of a knee injury. The hooker missed much of last season and has not featured since January , with Northampton believing there is "no immediate prospect" of a return to full fitness.

In an official club statement, there was no mention of Sharman's tweet, which was posted ahead of Farah's Olympic 5,000 metres final at London 2012 and read: "Good luck Mohammed running for Paki... I mean Great Britain..."

It was deleted shortly after it had been sent, while Sharman made a public apology and closed his Twitter account.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in