On 1/16/07, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> On 1/16/07, C. Michael Pilato <cmpilato@collab.net> wrote:
> > written, it didn't actually solve any interesting problem that didn't
> > already have a simple (albeit mildly annoying) workaround, and that the
> > feature and its maintenance were, by and large, unjustifiable baggage.
>
> What's the simple workaround? It's a very helpful feature if you have
> multiple patches in your tree. Or, am I misunderstanding something?
> -- justin
Yeah, i don't get the "mildly annoying" workaround either.
I use it to work on multiple changes in my gcc trees and manage them
all the time using this.
The only workaround i can see would be have more checked out trees, at
another 2 gig a pop.
I've already got 6.
Each probably has 3-4 changelists in it (they get moved to a temporary
tree when they are ready in order to do truly clean testing).
That's not only a disk space increase, it's also a factor of 3 work
increase in keeping these trees up-to-date and doing quick testing on
it. Now i've got to run the testsuite 18-24 times to get any coverage
at all of every patch, instead of 6 times.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 16 21:16:49 2007