On Wed, 17 Mar 2004 09:46:30 -0800 (PST) Jon Smirl <[EMAIL PROTECTED]> wrote:
> I am copying the v files. The branches get impact via single file symlinks as I > explained in > other mail. Only branches which use the external DRM. Branches that still have their own "internal" one should not be affected. As an analogy: Branches with their own "internal" copy of Mesa sources were not affected by the changes that moved 3D drivers to Mesa CVS and removed the Mesa source code from xc/extras/Mesa in DRI CVS. Felix > > After the switch I will use "cvs rm" on them. > > --- Ian Romanick <[EMAIL PROTECTED]> wrote: > > Michel D__nzer wrote: > > >>Jon Smirl wrote: > > >> > > >>>dri branches will also need to apply this patch > > > > > > Why? What happens on the trunk shouldn't affect them. That's the point > > > of a branch. :) > > > > I believe the intention is to *move* the ,v files. If that happens, the > > files will "disappear" from all branches. That said, I don't think > > moving (as opposed to copying) the ,v files is a good idea. We still > > want 'cvs co -D <somedate> xc' to work. > > ------------------------------------------------------- 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
