Good thoughts, Tim. I've created two Github issue:
- https://github.com/haproxy/haproxy/issues/762 <https://github.com/haproxy/haproxy/issues/762> (segfault) - https://github.com/haproxy/haproxy/issues/763 <https://github.com/haproxy/haproxy/issues/763> (uuid config issue) Best, Luke — Luke Seelenbinder Stadia Maps | Founder stadiamaps.com > On 17 Jul 2020, at 18:21, Tim Düsterhus <[email protected]> wrote: > > Luke, > > Am 17.07.20 um 17:55 schrieb Luke Seelenbinder: >> To follow up on this—is it easier if I create this as a GitHub issue? >> > > It will certainly not get lost in the depths of the email archive and it > allows to easily link commits to issues and issues to commits just by > mentioning the number in the message. > > Personally I create issues for everything, even if I fix them myself a > few minutes later. In case my patch isn't correct at least the issue > will still remain in the tracker. > > Best regards > Tim Düsterhus >
