No, it means you're using the wrong abstraction.
As you change your codebase, files are modified. To the untrained eye, it looks like this a simple linear progression of history, and you just want to record savepoints as you go along. CVS lets you pretend this is the case.
Actually, that's not the case at all. What you actually want to record is the changes you're making, and the relations between them. In the vanishingly small edge case where you never have any collaborators, never any experimental code, you never need to backtrack, you never need to work on more than one portion of the code at a time - this is isomorphous.
The rest of the time, it's not. CVS & SVN try to stretch the first abstraction to take care of these differences, but fail.
git makes you face up to the fact that your abstractions are wrong.