Routines quitting on first error condition

I would like to know if there is a good reason that recursive adds and
commits need to quit on encountering an error. It is a frustrating
behavior that makes processing large batches of files that have issues
a frustrating process.

For example, I recently had a set of Makefiles that ended up having ^M
line endings. Tortoise SVN refused to add any files beyond this file.
After fixing the first problem and starting the process again, it quits
on the second occurrence. If it would have continued through both of
these, I could have read the log and fixed both of them. Instead, I
had run the process several times - frustrating and time consuming.
The behavior that I would prefer is to record the error message in the
log and continue processing the remaining files in the task.

It sure would be a pain if a compiler would quite compiling upon the
first syntax error it finds...

Steve Holtz