Ben Collins-Sussman <sussman@collab.net> writes:
> > > What does "this change is simply growing too large" mean, in technical
> > > terms? Was the usual update-from-repos-into-locally-modified-wc
> > > process not working for this change, and if so why not?
> >=20
> > It means that I had modified in some fashion 26 source files already,
> > and felt pretty strongly that the work of getting the feedback stuff
> > Right was significantly large enough to justify it's own commit. The
> > problem is that there was effectively no way to partially commit my
> > changes without either breaking the tests or #if/#else-ing a simply
> > ridiculous amount of code. I chose to commit. You can flog me and
> > revert my changes, or you can start helping me code -- I'm indifferent.
>
> Wow, sounds like we could have used branches here. :-)
Yep, it sure does. In fact, I was going to do this. But with no
merge at the time, I opted out of using them. :-(
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 3 17:07:02 2002