Re: Merging the reintegrate-improvements branch back to trunk

> > Alternative: don't print subtrees and rev-ranges at all, unless --verbose
> > (or a new --bikeshed flag...) is given.
>
> Daniel - I prefer we have the aforementioned detailed error message
> (whatever its final form may be) by default. My thinking is that if
> --reintegrate fails, and the user knows that --verbose will give them
> additional information to solve the problem, then they are *always*
> going to repeat the merge with --verbose no? So why not just give it
> to them the first time?
>

You said it: because the error might be several screenfuls tall.

> Also, if you are dealing with an extremely large WC with a lot of
> subtree mergeinfo it can still take some significant time to calculate
> all this (due to the tree walk required). I think it might be
> frustrating to do the merge, wait, get the error, then be forced to do
> it again so you can get the useful error.
>

For "extremely large" wc's, *anything* takes a significant amount of time.

> Lastly, I don't like tying the quality of the error message to an
> option. Do we do that anywhere else? We'd have to add the -v option
> to merge just for this.
>

Not that I could find.

> Paul
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-07 08:32:02 CET