As for dropping - if you don't perform, you need to be dropped. If you score runs again, you should be picked again! It's really that simple. Frankly, he was a passenger in the side for far too long and other players could have done better. If he had found his form again in FC cricket, I'd have no problem with immediately putting him into the team again. I don't see why anything except performance should be the criteria for selection. Obviously, you don't want to drop someone after a couple Test matches, but I don't believe in sacrificing the next Test match in order to potentially win one a year from now.

I certainly think someone who has contributed as much as Ponting, Dravid, or Tendulkar need to be given more chances than someone like Yuvraj for example. Primarily because despite their streak, their past performance probably makes it likely that they'll snap out of it. But there's obviously a line that people draw at some point - I just tend to draw it a little earlier than others. I think a streak of 12-15 Tests is about the maximum for even a great player.

And as I keep reiterating - dropping for me isn't a permanent thing. I don't have this obsession with constantly bringing in 19 year old batsmen hoping they'll be good for the next 15 years. If someone is 35, is dropped and starts scoring again, I have no problem with picking them. I have no problems with Ganguly coming back into the side after he was dropped for example.

Then you have the situation where your replacement comes in, has 3 tests, barely has a chance to cement himself and Sachin is tearing up FC cricket and replaces him.

That really achieves nothing.

You also have the situation where your replacement comes in, averages 35, but again, Sachin is tearing up FC cricket. Do you drop the n00b?

I'd give any player more than 3 Tests, unless it's ridiculously bad. If he averages (say) 35 after two series (say 6-8 Tests?), and someone proven like Sachin is tearing up domestically, I'd drop him. If he is doing much better, he stays.