> Regarding CVS access, Brian, I get email from people, and I talk to > those people that have shown some investment. I've only added one or two > people. My stock answer when asked is that you should submit a patch or > two before we give access. Now one has. For the few people that have > shown some code or even a good understanding, they've turned me down > saying they're too busy.
My intrest at the moment would not be to use CVS to make/upgrade a driver - at least not yet. I'd be more intrested to know if there would be a way to add/upgrade documents in the CVS so that they'd become somewhat automagically available to everyone in CVS and in some 'community' section of http://dri.sourceforge.net/doc.phtml (with timestamp to show last handling date.) hence anyone could try to write doc and others could make additions/corrections to it if they'd like to and it would be versioned and ... I myself tried to make flowchart of sorts for 3 example drivers so that it would explain how things would go trough from OpenGL call down to hardware. This for 3 drivers like totally software, bits accelereted, all (T&L) accel. Would perhaps help ppl to understand the way it works. -- Janne echo [EMAIL PROTECTED] | tr acefhiklnptu utpnlkihfeca _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
