barry@python.org (Barry A. Warsaw) writes: > I think this one at least is fixed in pybsddb's cvs. Can you update > to the latest cvs? Not if I can avoid it. If I have to merge now, how can I merge the next time? Copying over the files won't work (because of the few changes I had to make), so I will have to apply patches. But how can I produce patches if I have to diff against some CVS snapshot? I don't want to keep the snapshot around, because that would mean nobody but me could merge the code the next time. Of course, if there was a 3.4.1 release or some such, merging would be easier: I would now apply the diffs between 3.4.0 and 3.4.1, and the next time the diffs between 3.4.1, and the then-current release. 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