Hello, On 06.05.2018 16:22, Kaartic Sivaraam wrote:
The blog looks pretty well written. I also read your proposal. It also seems to be pretty much well written. I like the way you explain things. Particularly, you seem to be explaining the problem and the way you're about to approach it well. The plan seems pretty good.
Thank you a lot!
I just thought of suggesting one thing which might possibly be redundant. I think you're aware of the fact that the Git project has Travis-CI builds enabled[1] which you could take advantage of to ensure your changes pass in various text environments. If you're interested in testing your changes (which I suspect you are), you might also be interested in 'git-test'[2], a tool built by Michael Haggerty. Unlike the Travis-CI tests which test only the tip of the change, 'git-test' would help you ensure that every single commit you make doesn't break the test suite (which is both a nice thing and is expected here).
I heard of it and used it a couple of times (for the micro-project and some other patch).
Sorry for the off-topic info about the tests in this mail :-)
You shouldn't be sorry. Nothing was off-topic; I found everything you said to be helpful! Every feedback is welcomed!
Hope you're able to achieve your goal as planned and have a great time during this summer of code!
Thank you one more time! I know it will be a good summer. Best, Paul Ungureanu
