On Mon, Jun 02, 2003 at 04:23:14PM -0600, Brian Paul wrote: > > Sounds like the Mesa directory re-org should happen sooner, rather > than later. > > I've been doing some research into CVS and it looks like there are two > approaches to doing the re-org: > > 1. Use the usual cvs add/remove/commit commands to move everything > around. This would work, but it would be pretty tedious and we'd sort > of lose the CVS histories. > > 2. Download the nightly CVS tarball to my machine, reorganize it, then > upload it to SourceForge and have the SF admins install it as the > new CVS tree. The one issue with this approach is that it would > effect all CVS branches. A benefit would be the ability to _really_ > remove the old, empty directories. > > I prefer option 2. > > My first step would be to wrap-up version 5.0.2 (bug fix release) and > get that out of the way. > > That would leave the embedded-* branches. Do those of you working on > those branches have any concerns?
Not really. When it's planned to merge them (at least embedded-1-branch)? > Mesa/ > src/ > mesa/ [...] > drivers/ Wouldn't be better to have the 'drivers' up one dir? That would would probably make it easier to people wanting to include the 'mesa' directory in other projects (such as DRI itself). (hmm... on the other hand they always need at least one of the drivers, so it isn't clear there is any advantage with this.) > common/ - reusable driver code > X11/ - X11 (XMesa) driver > osmesa/ - OSMesa drier > swfbdev/ - software fbdev driver > radeon/ - DRI/fbdev driver > radeon-es/ - subset radeon fbdev driver > r200/ ... > mga/ - DRI/fbdev driver > windows/ > beos/ > ggi/ > glide/ - was FX driver > dos/ José Fonseca ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
