On Fri, Aug 14, 2009 at 09:49:18AM -0600, Brian Paul wrote: > OK, the problem with these patches (as Keith commented on) is that > the build is broken between the patches. That makes git-bisect > difficult. > How about we combine these patches into one big patch that doesn't > break the build? The sounds good. I will (maybe next week) merge the first patch series (the tarball) into a single patch, and update the other patch series so that it does not break the build in each step. > >>Could you resend whatever prerequisite patches are needed? > >>Or maybe just hold off on patches until you get git-write ability? > >That's fine, but I would like to hear some feedbacks for such > >restructuring work. Even after I have git-write ability. > Of course. Posting patches for review before committing them is good.
-- Regards, olv ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
