-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All,
I'm intending to create a mesa_7_6_branch tomorrow (Friday) morning. As usual, this branch is intended for bug fixes leading to a 7.6 release. I'm open to discussion, but my preference is that the branch be used in the following way: - Bug fixes that will be in master and the branch be committed to master, then cherry-picked to the branch. - Bug fixes that will only be in master *or* the branch be committed directly to master or the branch. By whatever means, I want to avoid the situation that we're currently in with the 7.5 branch. We have numerous cases of patches being cherry-picked and merged both ways. This results in same patch showing up multiple times in the master commit log. Patches should flow in one direction through branches. Opinions? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqgDRAACgkQX1gOwKyEAw/I/wCdF9pte33FIn3Pp+UJOXZq2Xkf HgoAnAiTW0riG642uipvIF9Nbq4xK78K =IFQr -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ 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 Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
