> Aha! A specific file. I'm supportive of fixing that specific file. Now > if you can figure out how to do it and still allow merging between 2.6 > and 3.0 that would be cool. In the specific case, I think it's best to fix the 2.7 source, and then merge the changes into 3k. The 3.x version is still similar to the 2.x version, except for a number of additions (such as interning). The changes should probably then also merged into the 2.6 and 3.0 branches, to allow easy merging in the future. Backporting to 2.5 will become difficult; it will also become unnecessary. 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