On Thu, 2004-04-15 at 17:44, Jon Smirl wrote: > I've been down the branch path before. I have many thousands of lines of > changes. If I do all of them on a branch sometime in the future people might > decide to merge them. When that happens everyone will say there is too much code > and it is too complex to understand, break it up into small patches again. Then > I'll have to spend three months breaking things back into chunks. These will > then get nit picked to death and each one will take a month to get into the > trunk. A year from now I might have the functions merged. To avoid merge issues > I will have to continuously monitor the trunk and track each check in there and > apply it by hand to the branch.
That's not how branches have been handled in the DRI project. You may want to read the DRI CVS policies. Sounds to me like a strawman argument for piecemeal setting-in-stone of controversial changes. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
