hi INDiA
South Asian Views On Global News - Update 24X7

‘You Want Controversy?’ Kohli Slams Pak Journalist For Targeting Rohit With A Wry Smile

India suffered a historic loss against arch-rivals Pakistan in their opening encounter of the T20 World Cup in Dubai. The Men in Blue were completely outplayed by the opposition in all three departments of the game.

With this loss, India’s unbeaten streak against Pakistan in the World Cup events came to an end. Also, it was the first time India had lost a T20I game by a margin of 10 wickets.

Record breakers @iMRizwanPak and @babarazam258 posted the highest first-wicket partnership in Men’s #T20WorldCup history in #Pakistan‘s momentous win

Read more https://t.co/yh4mb4SuXa#INDvPAK pic.twitter.com/NOyVY1ivyD

— ICC (@ICC) October 25, 2021

It all started when Shaheen Shah Afridi dismissed Indian vice-captain Rohit Sharma for a golden duck with a brilliant in-swinging delivery in the first over of the match. India could never recover from the early blows and played the chasing game throughout the match.

Given their form and the way they performed in the two warm-up games, many had expected Team India to win the match quite comfortably but the result came as a shocker to many. Having said that, the way Babar Azam’s side played from start to finish in this blockbuster clash they deserved to win the match. 

© Twitter BCCI

During the post-match press conference, a Pakistani journalist asked a question that left the Indian skipper fuming. Raising a finger on Kohli’s team selection, the Pak reporter asked him if he made a mistake by not picking Ishan Kishan, who had played brilliantly in the warm-up matches, for this mega clash ahead of the ‘Hitman’.

Here’s how the conversation panned out:

“Will you drop Rohit Sharma from T20Is?” @imVkohli had no time for this question following #India‘s loss to #Pakistan.#INDvPAK #T20WorldCup pic.twitter.com/sLbrq7z2PW

— ICC (@ICC) October 25, 2021

“Do you think that Ishan Kishan should have played ahead of Rohit Sharma?” the reporter asked.

Shocked to hear this question, Kohli remained silent for a few seconds and then replied: “Really? It’s a very brave question. What do you think, sir? I played the team that I thought was the best. What is your opinion?”.

© Reuters

Despite hearing Kohli’s initial reaction, the journalist found nothing wrong in his question and defended himself by saying: “I am asking you”.

“Will you drop Rohit Sharma from T20 Internationals? You’ll drop Rohit Sharma?” Kohli repeated himself with a lot more seriousness.

“You know what he did in the last game that we played,” he enquired, reminding him of Rohit’s blistering fifty that he scored against Australia in their second warm-up game.

“Unbelievable” said Kohli before covering his face for a few seconds. He ended the conversation by telling the Pakistani journalist “Sir, if you want controversy, please tell me before, so I can answer accordingly”.

© Twitter BCCI

It’s okay to raise questions and point fingers at team selections after a team had just lost the match. But the journalists must keep in mind that the question that they are asking makes a little sense.

In the past, Kohli had received a lot of flak for getting into a fight with the journalists but on this occasion his reaction was absolutely on point. The way he controlled his anger with a cheeky smile and still made his point across was really commendable.

Tough day for #TeamIndia at the office, but we will bounce back in our next game.#T20WorldCup #INDvPAK pic.twitter.com/mYwYXVN6xc

— BCCI (@BCCI) October 24, 2021

After just one bad day in the office, targeting Rohit Sharma was just not done. For so many years, he has been one of the best limited-overs openers in world cricket and questioning his ability after just one poor outing was hard to digest for anyone who understands even a little bit of cricket.

Visa-Home Ad

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

gtag('set', {'user_id': 'USER_ID'}); // Set the user ID using signed-in user_id.