RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !

[Fabian Cenedese]

>Hmm, this is interesting. I have always been (and still am) of the
>opinion that one should always commit individual files, and never ever
>do a 'cvs commit' on the top level of a module. Why? Because top level
>commits usually create poor log messages (same for all files), and
>because it makes it far too easy to commit files that you have just
>made temporary modifications to (e.g. changing a make file to compile
>with debug flags) that you really don't want to commit at all.
>Oh well, I guess I must be a total idiot then...

Well, I also commit single files for the same reasons (even if that makes
me an idiot too). But before committing I sure do a test/update if there
has anything changed in the repo. So I do the same as cvs ci on whole
sandbox, just manually. Like that I never had any problems (well, with
committing, don't mention the committed source files :)

bye  Fabi