> Darn. Was hoping you'd missed that I'd put that question off :) > At this point, I'm still trawling CVS - I hope to have an estimate > in a day or so (work stuff permitting), or the end of the week at > the latest. My gut feel right now is that it's a couple of weeks > to finish trawling the CVS logs (geez you guys commit a lot of > changes) and checking them in carefully). Remember you are Patch Czar, not the slave of patches. You could restrict yourself to incorporate only patches that people propose. If you want systematic scanning, we could try to come up with a script that automatically reviews all commit messages of patches since 2.1.1 whether these mention an SF bug. We could then further automate scanning to produce the number of changed lines, to exclude 'large' changes. Perhaps anybody in the readership of this software already has code that does such things? Regards, Martin
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