Just a day after senior party leader and former union minister Kapil Sibal held the incumbent leadership of the Indian National Congress (INC) responsible for the party's streak of debacles in Bihar Assembly polls and a host of bypolls, Rajasthan's Chief Minister (CM) Ashok Gehlot has come out attacking the former over his criticism of the leadership, reports Indian Express.
CM Gehlot slammed Sibal for airing his views on Congress party's leadership woes in public. He tried to press that there was "no need" for Sibal to mention “internal issues” in the media. He also added that after every electoral loss, the party had shown “undivided and firm belief in the leadership”.
CM Gehlot mentioned that Congress had witnessed electoral setbacks in 1969, 1977, 1989 and in 1996, but came out stronger each time due to its "ideology, programmes, policies and firm belief in party leadership."
This came even as other party leaders like its Members of Parliament (MPs) Vivek Tankha and Karti Chidambaram backed Sibal's views and reiterated the same. Speaking in a no-holds-barred fashion, Tankha said, "Others may not speak because they have their own issues. I and Kapil have no other issues. Our issue is the revival of the Congress. And if people like us don’t come forward and speak about it, history will not forgive us."
Comments ↓
An Appeal...
Dear Reader,
As you are no doubt aware, Swarajya is a media product that is directly dependent on support from its readers in the form of subscriptions. We do not have the muscle and backing of a large media conglomerate nor are we playing for the large advertisement sweep-stake.
Our business model is you and your subscription. And in challenging times like these, we need your support now more than ever.
We deliver over 10 - 15 high quality articles with expert insights and views. From 7AM in the morning to 10PM late night we operate to ensure you, the reader, get to see what is just right.
Becoming a Patron or a subscriber for as little as Rs 1200/year is the best way you can support our efforts.
The embedded tweet could not be found…