Yes but I can't find the commit On Mon, Aug 21, 2017 at 6:03 PM <coreboot@fe80.eu> wrote: > Issue #62 has been updated by Stefan Reinauer. > ... >ron minnich
yes, paul, thanks, that's it, fa74e4705dbb5ecf5ba466fd6a9bc309f7e3e8bf On Fri, Jul 14, 2017 at 1:48 AM <coreboot@fe80.eu> wrote: > Issue #62 has been updated by Paul Menzel. > ... >ron minnich
No, this would still not have worked save that I upstreamed a fix to coreboot a few months ago and forgot to close this bug. :-) How do we put a bug # in a commit and have it close the bug? is that possible? On Mon, Dec 12, 2016 at 7:5...ron minnich
No, this would still not have worked save that I upstreamed a fix to coreboot a few months ago and forgot to close this bug. :-) How do we put a bug # in a commit and have it close the bug? is that possible? On Mon, Dec 12, 2016 at 7:5...ron minnich
No, this would still not have worked save that I upstreamed a fix to coreboot a few months ago and forgot to close this bug. :-) How do we put a bug # in a commit and have it close the bug? is that possible? On Mon, Dec 12, 2016 at 7:5...ron minnich
No, this would still not have worked save that I upstreamed a fix to coreboot a few months ago and forgot to close this bug. :-) How do we put a bug # in a commit and have it close the bug? is that possible? On Mon, Dec 12, 2016 at 7:5...ron minnich
No, this would still not have worked save that I upstreamed a fix to coreboot a few months ago and forgot to close this bug. :-) How do we put a bug # in a commit and have it close the bug? is that possible? On Mon, Dec 12, 2016 at 7:5...ron minnich