I would like a little guidance on how to handle patches during this 1.6 episode. My understanding of CVS tells me that 1.6 has forked from the main development tree. Any work done in the 1.6 branch will need to also be done in the main branch. Is this correct? If so, it means that all patches assigned to me need to be applied and tested twice, which involves completely refetching the entire tree, and rebuilding the world? Given that 1.6 appears to be mainly an exercise in posturing by CNRI, is it reasonable that I hold some patches off while I'm working with 1.6, and check them in when I move back to the main branch? Surely no one will stick with 1.6 in the long (or even medium) term, once all active development of that code ceases? Of course, this wouldn't include critical bugs, but no one is mad enough to assign them to me anyway <wink> Confused-and-in-need-of-a-machine-upgrade ly, Mark.
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