Will Estes
Will Estes
The idea seems reasonable, yes.
On Monday, 12 March 2018, 5:48 pm +0000, "Kang-Che Sung (宋岡哲)" wrote: > It looks like Automake 1.16.1 reveals a "make distcleancheck" bug for us. ([See the build log.](https://travis-ci.org/westes/flex/builds/352422245)) >...
Since this pr is generating build failures, I'm moving it to 2.6.6 to allow more time to sort out the issues you list.
And the retargeting stuff is merged in, so does the current tip of master do what you need?
Always submit a pr. There's no code to evaluate until that happens. On Sunday, 16 September 2018, 6:46 am -0700, Simon Sobisch wrote: > @westes / @Explorer09 > If no...
I would suggest that I perform the registration since it looks like approving access to scan results would best be done by me. Given their interest in disclosing scan results,...
The reason for registering after the next release is so that any clocks that get started by their findings can get my full attention, which they won't get if I...
My plan is that only tagged releases would be pushed by travis. Yet to be implemented and it's down in the queue, but it is there. On Wednesday, 12 June...
You're quite correct that COPYING and any other copyright notices need updated. I have a vague memory that some automated tool exists to do this, though.
Can you see about the conflicts that have ben introduced from the merging in of #489?