Re: Branching ext/standard?

> What I would do in your case is: > > (a) Tag the relevant files as they are today (i.e., PRE_RAND_REDESIGN or > whatever) > (b) Commit your move-around changes > (c) Commit the real changes (can be done immediately after (b), as long as > it's separate) The real changes are not ready... and I didn't want to start with it until I know the move-around is okay, since I don't like to work for nothing. I'll commit the move-around changes then, but it will be broken, maybe even normal build, because it is EXPERMENTAL, and I didn't do much testing, it is simply not ready, it's about the idea. > (d) Cross your fingers :) I know who to blaim if ppl complain about a broken CVS ;-) I'll do this in 10 minutes unless you change your mind... Thanks for the advice, Jeroen PS: > having the tree broken for a few hours or even a couple of days under the This quite optimistic!