diff options
Diffstat (limited to 'content/entry/debugging-neomutt.md')
| -rw-r--r-- | content/entry/debugging-neomutt.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/entry/debugging-neomutt.md b/content/entry/debugging-neomutt.md index 714aced..1f60803 100644 --- a/content/entry/debugging-neomutt.md +++ b/content/entry/debugging-neomutt.md @@ -22,7 +22,7 @@ With some more assistance, I then used GDB to check the variable values and foun Now that the cause of the crash was understood, Flatcap patched gpgme so it could handle partially defined keys. I pulled the patched branch, recompiled, and tried to open the buggy email again. No crash! -Flatcap invited me to open a Github issue so I could take credit for finding the bug. I informed him I couldn't do that because [I don't use Github](/2021/05/31/dont-use-github/). So he just opened [the issue](https://github.com/neomutt/neomutt/pull/3137) and mentioned me instead. I looked over it for review and approved. +Flatcap invited me to open a GitHub issue so I could take credit for finding the bug. I informed him I couldn't do that because [I don't use GitHub](/2021/05/31/dont-use-github/). So he just opened [the issue](https://github.com/neomutt/neomutt/pull/3137) and mentioned me instead. I looked over it for review and approved. I thanked Flatcap for creating Neomutt. I really enjoy using it. I'm glad I was able to contribute to such a fantastic email client. The only reason this interaction was possible is because Neomutt is free software. If it were proprietary, I couldn't have debugged it with GDB. I probably wouldn't have gotten to interact directly with the developer who writes the software I use. I'd probably be stuck waiting days or weeks on a response from an opaque company where I couldn't even review the patch or get credit for reporting the bug. |