Re: TSVN + non-server operations + errors

Peter Mounce wrote:

> If I set off a really big add operation, and it errors out (because of
> in this case, inconsistent newlines), it would be really nice if TSVN
> didn't cancel the rest of the queue (since if I add thousands of little
> files to a queue (which was my use case), it's guaranteed that I'm not
> going to pay attention to it until I reckon it's complete - I'll be
> making coffee), but carried on, and remembered which files caused
> errors, and reported at the end for me to fix whichever files, but
> successfully added all the ones that were ok to add.
>
> Since Add is not an operation involving the server or atomicity, can
> TSVN step in to improve the workflow for cases like this? Can the
> progress window be changed so it can filter out all items that didn't
> cause an error (for example)?
>
> Or perhaps TSVN could remember the original operation, and the progress
> window could redirect me back to the add dialog, with the erroring file
> unticked, but the rest of my selections remembered and intact? I think
> I would prefer the "just get on with as much as you can please TSVN, and
> tell me at the end which files were problematic".

You should ask for this on the Subversion mailing list. It's the
svn_client_add() function that aborts and doesn't go on with the rest of
the files.

Sure, it would be possible to hack around this. But I don't like such
hacks at all.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org