For example - the review process that is happening is a move in the right direction, but CVS makes it awkward and fault prone - git supports doing it correctly.
OTOH, I think it is natural that on the initial change to git it would be used mostly like we use CVS, and then as people get acquainted with it, better practices start to catch on. We cannot get the better practices without the switch
Back to what Tim was saying, yes, we can stay on CVS and have some developers use git. But extending the practices that git allows to all the core devs does have a benefit.
My opinion hasn't changed in that it's not an urgent thing. I just hope - as I mentioned earlier - that Eclipse support doesn't hold us back completely because there are project-wide benefits to it that seem to me bigger than the (understandable) inconvenience.