https://bugs.kde.org/show_bug.cgi?id=390096
--- Comment #7 from Andrew Crouthamel <croutham...@gmail.com> --- (In reply to Nate Graham from comment #5) > Testing out the revision on your own hardware and leaving a review comment > would probably be the most productive course of action! ;) What's the best way to test this since it will need to test my hardware key? Is there a good procedure for these sorts of things that need hardware access? I guess a Neon Dev Unstable USB stick? But, I'd need to patch this code in. If anyone could help me out with a test procedure, I'd be glad to try it. -- You are receiving this mail because: You are watching all bug changes.
