Ok, thanks - I am looking forward to further collaboration and patches. As said, the format of the test tree is not set in stone and I'd be happy to change it and discuss alternatives - whichever way is best. It is also possible to store more stuff - that is what the thing consumes electrical energy for. I.e. if the CCID4 folks want to store stuff, that's welcome too. | > | Aha. I see what you mean now. I think the best thing to do here is to | > | label each block of code introduced, that is specific to a version, | > | with the version of the document used. | > That's why I thought a separate branch would be nice - it keeps all documentation and patches together | > so that even after some pauses in between one knows where the code came from and what it was good for. | > | | That's fine by me. - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
