On Thu, Apr 30, 2009 at 12:04:16AM -0700, Christopher Lee wrote: -> On Apr 26, 2009, at 12:01 PM, C. Titus Brown wrote: -> -> > The following branches should be considered for merge into master: -> > -> > runtest_single (author ctb, reviewed by ialbert) -> > cleanflag (author ialbert, reviewed by ctb) -> > review_issue40 (author ctb, fixes obvious bugs -> leec) -> > nicer-error (author ialbert, reviewed by ctb) -> -> I pushed all of these to master today. -> -> > Finally, the following branches are still under discussion on the -> > mailing list and should remain: -> > -> > must_close & review_must_close -> -> must_close was resolved between Titus and me a while back; a much -> simplified version of this was agreed on, and pushed to master. We -> can get rid of both of these branches. -> -> > ossystem_quote & ossystem_quote_mkarg -> -> These were made obsolete by popen_tmp, which has also been pushed to -> master today. -> -> > xmlrpc_random_port -> -> I merged this to master too. Works for me on all platforms; gets rid -> of annoying "failed to acquire a port" testing problems.
Re all of the above, Fantastic! That looked like a lot of work... so congrats on getting it done ;) One question: should I delete, or just rename to something like 'zzz_' + original? The following branches are under the gun: buildbot-fixes cleanflag must_close nicer-error ossystem_quote ossystem_quote_mkarg popen_tmp psu-tests-branch review_issue40 review_issue40_x review_must_close runtest_single runtest_single_x sqlite_server_info testfix xmlrpc_random_port I have no objection to leaving them around, as long as we can distinguish them as "no longer under consideration" somehow. -> I also pushed sqlite_serverinfo to master. I saw this -- is there a description of what this branch is anywhere? I haven't been paying attention to the sqlite e-mails -- is it in there? ;) thanks, --titus -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
