This problem is massively helped by using git as your front end to SVN. The key feature is that in git you can re-order commits and even retrospectively move commits onto different development threads. I can't count the number of times that fixes have occurred to me out of order.
On Wed, Nov 3, 2010 at 9:01 AM, Gilles Sadowski < gil...@harfang.homelinux.org> wrote: > Also I'm not going to "svn co" a fresh copy of CM every time I > encounter an issue that should have been better dealt with *before* the > changes I'm currently performing (I already have two active ones). >