Greg Stein writes: > Note that some of the problems stem from CVS access. Much Guido-time could > be saved by a commit-then-review model, rather than review-then-Guido- This is a non-problem; I'm willing to do the arcane CVS manipulations if the issue is Guido's time. What I will *not* do is do it piecemeal without a cohesive plan that Guido approves of at least 95%, and I'll be really careful to do that last 5% when he's not in the office. ;) > commits model. Fred does this very well with the Doc/ area. Thanks for the vote of confidence! The model that I use for the Doc/ area is more like "Fred reviews, Fred commits, and Guido can read it on python.org like everyone else." Works for me! ;) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> Corporation for National Research Initiatives
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4