ch
ch
> hmm, you'll need to follow the developer guide for commits and code before this is going to get attention? Thanks for pointing this out, I've revised both the commit...
> take a second and look over the frrbot results and fix them. Again nothing will be looked at until coding standards have been met. Okay, I’ve updated the code.
> I think there's a basic issue here, that's worth asking about. This code makes library changes to expose some inner details of the vty library messaging, and then uses...
> yes, no argument that flow-control is good, and buffering endlessly isn't. but I'd rather not start hard-coding decision-making in each daemon's functions; that's hard for us to maintain. I'd...
> yes, no argument that flow-control is good, and buffering endlessly isn't. but I'd rather not start hard-coding decision-making in each daemon's functions; that's hard for us to maintain. I'd...
Hi @riw777 , I noticed that this PR is now marked "do not merge". Could you let me know the reason and what I should change to move it forward?...
rebased to new master, resolved conflicts